C=consultant
M=Me
D=my Dumb boss

M: so how are you guys planning to implement the block all accounts feature?
C: oh it should be easy! We will just loop over every account and lock it!
M: what about implementing a flag that just blocks anyone from accessing the site till further notice?
C: what? I’m sure it’ll work. Just need a list of all accounts, we don’t need anything fancy!
M: what happens when we want to revert back to the pre-block state?
C: oh, so we will just unblock everybody
M: even people who were previously blocked for good reasons?
C: i guess so, unless you think otherwise
M: we r….
D: listen! We just need to be able to block all accounts, who cares about this details! So long as we block all accounts! We need this nuclear option in case something bad happens…
M: but what about when that bad thing passes and…
D: when it passes it passes who cares!

Arghhh so much rage here… like first at the stupid engineering design of looping over all of the accounts instead of using a simple flag. Like 1 http call (from one microservice to another) is a lot better than O(n)… not to mention, we won’t have to deal with failures and retries.

And second for my boss being a dumbass… ok you deal with being to afraid to unblock people after we used this “genius nuclear option”!

I'm so fucking done with this shit. If someone forgets every git command every single fucking tim le is ok to ask. Every time someone asks advice on how to write a fucking retarded workaround (out of lazyness, because fixing their own code is too much to ask), it'a ok.
The *ONE* fucking time i ask the name of the fucking function to generate a filter via code using their fucking cms? "you should do that via gui!" "who cares if there'll be conficts with git, just manually redo everything in production!".
God fucking dammit how can you even have the balls to complain about terrible planning and stuff not working if that's your fucking mantra?!

Sometimes I really feel humiliated in my lab.

We have several presentation/discussion groups in my lab that meet once a week or so where members present their progress reports. Generally people in my lab are not so enthusiastic about them. Which is okay, I also don't like doing presentations, but you know, you have to improve somehow and get feedback somehow.

So I've been in a really passive group for a while and I decide to join this other group since they seem to have good discussions, but nope fuck me.

The first time I present, the professor doesn't show up since he has some meeting, so obviously nobody cares to show up. And I'm there presenting for a guy who is half comatose. Alright, I guess that's the price for joining a new team, it's gonna get better next time.

Second time. Spent all night to prepare my presentation and been training my model for two weeks. I am actually really happy with the results of my networks. But the enjoyment of showing some good results, I shall not have.

Meeting leader doesn't show up. Two guys who should present don't show up. Professor doesn't show up. A different professor substitutes him and has no idea what I am talking about and asks stupid questions that don't really have an answer. Fuck me, I'm so angry, this shit is a waste of time. If you don't show up, care to fucking send an email or a message on slack, but guess you're too fucking retarded to even do that.

I'm so done with this. I've gotten better feedback from reddit, than what I've cumulatively gotten from my laboratory. I'm a moment away from walking up to the meeting leader and telling him that the meetings are stupid and a waste of time. Don't get me wrong, my professor is really nice and knowledgeable, but he fails to see that some people in the laboratory are shit.

What do I do? How do I deal with these people? Right now they're planning a trip! Why are you planning a trip? WHAT ARE YOU REWARDING YOURSELVES FOR? YOU HAVE DONE NOTHING IN WEEKS? omfg

So at the moment, I'm currently reviewing the API specifications that got written up as the other developers haven't bothered to update it themselves. When you think about it, that's kind of dumb. If you are in charge of a particular function, it should be your responsibility to maintain documentation.

Anyway I'm cross referencing to what I see that has been done in the source code and finding way too many inconsistencies across specifications and implementations. Even parts where they have the exact same data, the structures are completely different. Or some parts have been documented but are not in the implementation, or vice versa. SO I can't tell which is the correct one!

I've just joined a new company out of despair after several month out of jobs without being able to even get interviews.
I've been warned about the code being a bit behind with modern Android stack, they needed to migrate from rx to coroutine and compose is not a priority at the moment.
Fine with it, I like handling and planning migration, that's a nice challenge.
But if only that were the only problems !! Far from it, the code is a formidable mess, I've never seen so much amateurism... Most of it was written from the previous Lead Dev who stayed there for years and touched everything with their very bad practices.
I don't even know where to start honestly...
While the code is in Kotlin, it stink Java. Nothing wrong about Java, but if you code in kotlin, you need to understand what kotlin try to achieve. And that's not the case here. There is freaking nullable everywhere, for no reason at all, the data classes contains lot of var in their constructors, equals are override to compare only one or 2 params and no hashcode override with it.
Sealed class, what for ?! Let me just write a List<Pair<Enum, Any>> and cast your any depending on the enum !
Oh and you know what, let's cast everywhere, no check, and for once no null safe, there is enough nullable in the code !

What about the reactive part ? well let's recreate a kind of broken eventbus with rx ! Cause why not ?!
The viewmodel observable don't contain data, they just contain enum for the progress of the states we're checking.
In the viewmodel function we update that enum states and emit it to be observed and make the data available as a var for the view to pick it up when needed.
But why put the business logic in the viewmodel, let's put in the views, and grab and check the variable contain in the viewmodel whenever it fits.
Testing the business logic ? uh let me just test my variable initialisation in the viewmodel instead.
The vm, the views, make about 2000 lines, the test over 3000, and not a single test really test the business logic in it ! I've made big refactoring we're all the tests stayed green, while the function are full of side effects ! WTF ?!
Oh and what about that migration from rx to coroutine ? well better not break the existing code and continue writting like rx, everything is cold flow ! We just need to store a boolean saying if we already did our call to the data layer then we decide to start our flow or not.
As for the RecyclerView, having too many viewHolder is just so annoying, let's put all our different views in one, and hide what we don't need.
Keystore has been push on the repo, but it's private no ? So who cares ?!
And wait i'm not done ! Some of the main brick of the apps depends on library that hasn't been updated for years, and you know what... yes they were hosted on Jcenter and it's only now that they decide to do something about it, we we're warned about the sunset of jcenter 2 years ago !!!!
So what about compose ? What do you want with compose ?! there is no design system in that app obviously, so don't even think about it !
And there... among all of that mess, I'm supposed to do code review... how the fuck do you do a code review when all the code that is around stink ?!
And there is so much more but by now I'm afraid you're thinking i'm just pissing on the old code like everyone... but damn I guarantee, that's the worst code I've ever seen, and i've work on more than 15 app from small to big on different contract with a lot of legacy code, but nothing that bad !