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
Just very diplomatically told the VP of Engineering to kick rocks (fuck off) for calling me at nearly 9pm to talk about project planning for a thing that isn’t even in active development.
Asked point blank if we were dealing with a life or death thing. He said no. I replied “then we can talk about this tomorrow”.
He balks and tries to tell me how important it is.
I cut him off “I wasn’t asking you, I am telling you it’s a quarter to 9 and I’m at a bar. This call is over. We’ll talk tomorrow. Good NIGHT”. With as much aggression and pissed off emphasis as I could muster on the ending.
Stay tuned to find out if I still have a job after this.10
Over the course of a few months, I began to suspect my manager disliked me on a personal level. I decided to be proactive and invited him to a meeting on "Improving our working relationship" - he showed up 5 minutes late and fired me.12
Interviewer: For this next code challenge you will not be allowed to use the internet, or an IDE.
Interviewer: OR a keyboard OR a mouse. I will be verbalizing the code to you and you need to memorize it and tell me where the bugs are.
Interviewer: We must do this exercise to know how you are as a dev without any performance enhancing “aid”. This way we can understand where you are truly at skill-wise, and what you are truly worth from a compensation perspective.
Dev: If I get a job with you will I be allowed to use the internet and an IDE and a keyboard/mouse?
Interview: Of course you would! Getting anything done without those is just about impossible. We just need to evaluate you without them to see how good you REALLY are.
Just got this little stinker added to my board this morning….
Ticket Title: Weird shit going on in app
Ticket Description: (blank)
Attachment: <Screenshot of app logo>
Manager: Well what do you think is causing it?
Dev: Causing what?? This ticket doesn’t describe anything at all
Manager: Well it’s a bunch of different things! The ticket is just a high level summary. Now how long do you think it’ll take to fix?
AHHHHHHHH I MADE AN OFFER ON A HOUSE
AHHHHHHHHHHHHHHHHH THEY ACCEPTED
AHHHHHHHHHHHHHHHHHHHHHHH INSPECTION DIDN’T TURN UP ANYTHING HORRIBLE
First we were called "rockstar" developers.
Then HR started using "heroes".
Then "tigers" and some confused associates who didn't get the memo used various other big cats.
Now they're starting to call us "product warriors".
PM in daily: your turn. what have you done yesterday?
me: so i finished my PR for feature x and now i'm only waiting for review feedback there, so i can close this ticket today if no major rework is required-
PM: this is not what i asked, i don't want to know what you did, i want to know what was done.
me: uhh... okay, also i started working on task x
[note: task x, a task per definition involving a large amount of research, was very coarsly defined and it wasn't even clear to the PM what he exactly expects from me, and we agreed that the scope needs to be refined in the process],
so as a first step, i started doing some general investigations to get an overview of the topic and learn about concepts a and b-
PM: again, i don't want to know what you did, i want to know what was done.
me: okay well, i have DONE basic research on topic xy and collected information-
PM: this still does not answer my question, what's the deliverable?
me: ...so uhhh.... i read papers? i researched info online and collected and prepared information and links in a presentation which i'm also planning to present to the team-
PM: okay, can you please split your jira task in subtasks so everyone knows exactly what you're working on? otherwise we have no idea what you're doing.
for fuck's sake, shut up. just shut up19
I hired a guy on upwork. His english is shit. But hes done the work correctly. Fast forward today he asked me "off topic question but do u have any female friend who can accompany me to fuck?"
WTF IS THIS SHIT
That is not professional AT ALL. I dont give a shit about the fact he cant get no bitches so hes begging me as if im some kind of a pimp. On upwork?? Gtfo.
Now i understand why companies want to hire only people with college DEGREES because they have went through the process of conforming and dont ask stupid shit questions. Eliminates a lot of bullshit and Neanderthals like this guy
Me 5 years ago : "Guys we are gonna have a perf..."
CEO : "Not now, we need to deliver that functionality asap"
Me 3 years ago : "Guys, performances/scalibiluity will hit us like a trucK'
CEO : "Not nowem a new functionality needs to be done ASAP"
Me 1 year ago : "We are gonna be hit by a tank. We won't even understand what happens"
CEO : "I'm sure we can manage"
2 Days ago : Plateform quasiment down, response time in MIONUTES instead of milliseconds, database on fire.
CEO : "WHAT THE FUCK !!! GO FIXC I ASAP WE CANNOT HAVE THAT SHIT HAPPEN".
This is a brief summaru of working in a startup.11
Hey, Root? How do you test your slow query ticket, again? I didn't bother reading the giant green "Testing notes:" box on the ticket. Yeah, could you explain it while I don't bother to listen and talk over you? Thanks.
Hey Root. I'm the DBA. Could you explain exactly what you're doing in this ticket, because i can't understand it. What are these new columns? Where is the new query? What are you doing? And why? Oh, the ticket? Yeah, I didn't bother to read it. There was too much text filled with things like implementation details, query optimization findings, overall benchmarking results, the purpose of the new columns, and i just couldn't care enough to read any of that. Yeah, I also don't know how to find the query it's running now. Yep, have complete access to the console and DB and query log. Still can't figure it out.
Hey Root. We pulled your urgent fix ticket from the release. You know, the one that SysOps and Data and even execs have been demanding? The one you finished three months ago? Yep, the problem is still taking down production every week or so, but we just can't verify that your fix is good enough. Even though the changes are pretty minimal, you've said it's 8x faster, and provided benchmark findings, we just ... don't know how to get the query it's running out of the code. or how check the query logs to find it. So. we just don't know if it's good enough.
Also, we goofed up when deploying and the testing database is gone, so now we can't test it since there are no records. Nevermind that you provided snippets to remedy exactly scenario in the ticket description you wrote three months ago.
Hey Root: Why did you take so long on this ticket? It has sat for so long now that someone else filed a ticket for it, with investigation findings. You know it's bringing down production, and it's kind of urgent. Maybe you should have prioritized it more, or written up better notes. You really need to communicate better. This is why we can't trust you to get things out.
I quit and my last day is next week.
Apparently management has decided that I should spend my last day implementing a new feature for a customer where I have been the only developer, and release it to production (without first implementing it in test) the same day. A feature that potentially could cripple a whole workflow if done wrong.
Of course I advised not to release untested code to production on a friday, just before the only person that knows how it works leaves the company. But no, “the customer reaaaaaally wants it before summer, so just be careful not to write any bugs”.
I’m not saying that I’m intentionally gonna write bad code - but if I do, I’m not gonna pick up the phone when it calls.19
*CTO in panic, as always, invites everyone to the war room*
CTO: We have a MAJOR problem where 0.0001% of our customers are not receiving SMS confirmations.
Me: Cool. But, 0.0001% is very less compared to the other problems we are solving.
CTO: You don't understand, this is critical issue that needs to be addressed immediately.
Me: But even those.0.0001% customers are receiving e-mail confirmations, so this is not even blocker as we have other channels working.
CTO: I am emotional at this point. You need to prioritise this now.
Me: Okay, do we know the root cause of this problem?
Engineering head: we have blacklisted those numbers in past as our system detected them abusing our platform.
Me: Cool. Let's whitelist them, nothing much to worry here.
CTO: Floyd, you need to understand that 0.0001% of the customers are not receiving the SMS and the solution you are proposing is incorrect.
Me: Okay, what do you suggest?
CTO: We stop sending the SMS to all the customers.
Everyone on the call: 😨18
Micromanager: "Hey, Root!
Since you're back, and still not feeling well, we have an easy ticket for you: Rewrite the slack integration gem! Oh, you don't have to re-implement all of it, just make sure it all works the same way it does now. That bitch you worked with once over a year ago who kept throwing you under the bus to management and stealing credit for your work? Yeah, she wrote the original code like four years ago. It's perfect, so don't touch it. but she can fill you in on all the details you need and get you up to speed on how to test it.
But yep! It should be simple. and I just knew you would love this ticket, so I saved it just for you. Nice and quick, too, to get you an easy win.
You know, since you have to repair your reputation with product. and management. and the execs. and the rest of the team. and me. Yeah, product doesn't trust you so they don't want to give you any tickets. They just can't trust you to get them out and have them work. So you have a lot of hard work to do."
Spoiler: The bus-thrower wasn't much help. (Surprise.)
Spoiler: The ticket was already in my backlog -- one of a grand total of two tickets.
Spoiler: I don't find the ticket fun. Maybe if I was to write the entire implementation with a nice DSL? but no, "don't touch the perfect code." Fuck you.
Spoiler: It isn't going to be nice or quick. But, she (micromanager) is looking to lose me, so that really is an easy win. for her.
And. just. argh. fuck you. i've been exhausted and dying for well over a year, but you've kept ignoring that (and still are, despite me providing goddamn legal forms from fucking doctors stating it in plain fucking english, which you also fucking ignore), and you just keep piling on the work and demanding the ridiculous of me despite it. Yeah I can pull it off sometimes. No, I really shouldn't, and I'm surprised I can. (also, "Time off? What, and lower your productivity even more? ____ doesn't even take vacations. And how are you doing on that ticket?") And no, none of my tickets have ever had any fucking problems. Not even when there are upstream service outages. Not. a. single. fucking. one. Ever. And the only things I've ever missed were things that bloody product never put in the fucking ticket, so fuck you with your "repair your reputation" bullshit.
god, i fuckiNG HATE THESESTUPOID ANWETLJAF SAJEWTKW BITCHFACEDUCKFUCKERS
Why the FUCK am I still fucking working here?
Right, because I've been burned out and dying so much I can't pass a fucking interview so I can fucking leave.
ugh. Anyway. If you ever find yourself starting work at a Cali fintech company whose internal mascot is a very fine duck? Just run. I absolutely guarantee you will be miserable.14
If you protect a PDF from copy-paste for no reason at all, please go die slowly and agonizingly in a fire27
micromanager: "Quick and easy win! Please have this done in 2-3 days to start repairing your reputation"
ticket: "Scrap this gem, and implement your own external service wrapper using the new and vastly different Slack API!"
slack: "New API? Give me bearer tokens! Don't use that legacy url crap, wth"
prev dev: "Yeah idk what a bearer token is. Have the same url instead, and try writing it down so you don't forget it?"
Slack admin: "I can't give you access to the slack integration test app, even though it's for exactly this and three others have access already, including your (micro)manager."
Slack: "You can also <a>create a new slack app</a>!" -- link logs me into slack chat instead. After searching and finding a link elsewhere: doesn't let me.
Slack admin: "You want a new test slack app instead? Sure, build it the same as before so it isn't abuseable. No? Okay, plan a presentation for it and bring security along for a meeting on Friday and I'll think about it. I'm in some planning meetings until then."
This job is endless delays, plus getting yelled at over the endless delays.
At least I can start on the code while I wait. Can't test anything for at least a week, though. =/14
the ultimate dick move: invite your dev to a meeting, scheduled a few weeks ahead, with title "performance issues", without any further comments or notice in advance. when dev, seeing this invitation and feeling kicked right in the face, asks if this meeting is about a certain project or their individual working performance, just answer "both" without any further comments. if they have any more questions about it, just tell them you have no time to answer because meetings.21
I just had my first "Microsoft you have a virus on your computer" scam call today and I managed to waste 29 minutes of their time, collect 4 numbers to report and call the guy and asshole in the end.7