AboutBurnt out from dealing with assholes. trying not to loose all my noodles.
Skillsgetting irritated at the smollest things because I'm past dealing with bullshit
Joined devRant on 11/25/2020
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Manager asked if I want to reconsider my resignation while reiterating that they cannot match the other company's offer.
Idk what the hell makes them think they can bargain without anything to bargain with in the first place.14
Employer made a mistake in making me interview dev applicants because they gave me a glimpse of how badly unskilled the market is... and how they are worth more than my current payscale.
Thank you for the much-needed sobriety from impostor syndrome.7
So apparently they will commend you for your reliability because you fixed a critical bug OVER making sure no critic bugs get into prod.
Fuck this place.
Context: was in a project where I took care of most of the analysis and implementation. Now I'm not longer part of the project, bugs were sprouting left and right and mgmt are congratulating these bug heroes for fixing shit THAT SHOULD NOT EVEN BE IN PROD. Fuck this shit.5
I have been flipping both my middle fingers at every chance I get while working.
Occasionally dropping enraged expletives here and there while I'm on mute.
I'm so excited to get out of here.1
A long time back, we were coming up with a strategy for a feature request. While discussing, my senior and I said something simultaneously, I backed out while he continued talking.
Once he was done, he turned to me and asked me what I was supposed to say. Shy as I was, I said, "never mind", even though I know his solution was workable but could have potential issues.
He responded with "No. Let's hear it." And we ended up using my suggestion.
That was the most empowering point of my career tbh. Not only was he willing to hear me out, but he also insisted that I be heard. I have learned so much from the people I worked with, but that one stands out. I try to extend the same attitude towards everyone I deal with, especially the juniors unsure about their footing in a new environment.1
All the meetings I had for the bug in rant: https://devrant.com/rants/4364259/...
But if I had to choose the most useless, mindnumbing one, it's the one where they invited the wrong user group.
Please be either disorganised or incompetent but NOT BOTH!
Ba was being fussy about a bug that was “blocking” a feature they are developing. I’m new to this project and I have seen the component less than 5 times but ok, I’ll take it.
Reproduced the bug and found out it is a case that has not been handled before. Came up with possible solutions, sent it to ba so they can analyse, maybe reach out to users, then choose or suggest a fix. That should be the end of it, right? No.
Did meeting to discuss root cause and proposed fixes but asshole still wants to reproduce and prove there is a bug (BUT WE ALREADY AGREE THIS IS A BUG????). Then insisted on meeting with users TO REPRODUCE THE BUG (AGAIN???). Then the meeting they scheduled was with the wrong group of users (WHAT THE FUCK?!) and still they went on to “demonstrate” a bug that was NOT what I was working on. Even had the gall to tell me to prioritise this unknown bug over the one I had been investigating on (both were “blocking” them). Took me all my self control to remain professional.
Now they want to close the bug because they cannot “reproduce”. HOW ABOUT YOU FUCKING FOLLOW THE REPRODUCTION STEPS INSTEAD DECIDING THE STEPS ON THE FLY?!
The amount of time I have spent talking to (and raging over) this guy would have been more than enough to implement all the proposed fixes. I knew it was a delaying tactic for their feature but the sheer amount of incompetence and willingness to waste everyone’s time is both amazing and infuriating.1
"We don't want to enforce documentation because no one reads them"
- every comment in every process improvement workshop in our company
Ok. Some points:
1) It takes a special kind of person to read a whole doc.
2) They're not there to be read leisurely. They are there for reference.
3) No one is reading them because you are not making people do them and instead rely on word of mouth bullshit.
4) Why are we doing this exercise if we are NOT going to improve anyway?10
Me: Out of curiosity, why didn’t you introduce unit testing into your project? I mean, you're the only dev. You could have done it!
Applicant: no one in the company was doing it, so I didn’t do it.
I’m not encouraging anyone to lie in their interviews, but please give a better answer than that. :/8
I have nothing against old devs. We are all moving in that direction anyway.
My problem is with devs who DO NOT LEARN AT ALL regardless of seniority. FUCK YOU. My team hired a dev with almost 20 yrs of exp. They were assigned to update a library ( +2 MAJOR versions) on a midsize critical project and they did it WITHOUT TESTING.
Hundreds of lines affected. What is a sane dev to expect? A fucking bug parade, of course!
To be fair, the codebase is over a decade old. No unit tests. BUT THAT’S WHY I GAVE THEM THE TOOLS TO TEST the old library against the new one even before they started!!! And they didn’t even open it until I probed them on the tests at the end.
TLDR shit got rolled back in prod twice (almost thrice), item got transferred to me. When they found a bug, the asshole tried to pin it on me with a very nicely written email. Attached with a git commit THAT WAS THEIRS.9
Hey asshole, when I say it's 10 dev days, it does not include your functional analysis.
We don't have a choice?! HOW ABOUT YOU DO YOUR FUCKING JOB WHEN YOU ARE SUPPOSED TO?
Ah. Two months more in this shithole.3
Daily standaups are supposed to last 15 mins for the whole team, not 15 minutes per person.
We want to know how you are progressing, not your whole life story! Unlike you, we've got jobs to do!!! 😡22
Team cicd guy resigned sometime ago and he was such a big dick before he left. Contributions have always been suboptimal, there's always a pipeline broken. Very brittle scripts. During kt, he was so up his ass and was not willing to trll us how things worked because it needed prior knowledge in jenkins and groovy. All requests for changes (because his work was stoooopid) were "NOT POSSIBLE".
Shithead didn't know I maintained the pipelines in my previous project 🙃
I took over the maintainance now and I want to burn his soul in hell. Hacky as fuck. Adding a new component literally breaks all the other project. I'm tempted to rewrite the whole thing but I'm also out of time 😑
How about he learn jenkins and groovy before he touches another job.
I resigned due to a mixture of burn out and bad management. I've reached a point where my opinion of the company is so low is giving me anxiety to stay.
Now i need to interview for my replacement. I feel like if I pass someone good, I'm essentially giving them a career roadblock.5