Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "lovely feature"
-
Kind of rant.
Why doesn't the cat sit on the keyboard?
At least my two cats just love that place. Perhaps a feature request?11 -
So Friday afternoon is always deployment time at my company. No sure why, but it always fucks us.
Anyways, last Friday, we had this lovely deployment that was missing a key piece. On Wednesday I had tested it, sent out an email(with screenshots) saying "yo, whoever wrote this, this feature is all fucked up." Management said they would handle it.
The response email. 1(out of 20) defects I sent in were not a defect but my error. No further response, so I assume the rest were being looked into.
In a call with bossman, my manager states that the feature is fixed, so I go to check it quickly before the deployment(on Friday).
THERE IS NO FUCKING CODE CHECK-IN. THE DEV BASTARD JUST SAID THAT MY USECASE WAS WRONG, SO MY ENTIRE EMAIL WAS INVALID.
I am currently working on Saturday, as the other guy refuses to see the problem! It is blatant, and I got 3 other people to reproduce to prove I am not crazy!
On top of that, the code makes me want to vomit! I write bad code. This is like a 3rd grader who doesn't know code copy-pasted from stack overflow! There is literally if(A) then B else if(!A) then B! And a for loop which does some shit, and the line after it closes has a second for loop that iterates over the same unaltered set! Why?! On top of that, the second for loop loops until "i" is equal to length-1, then does something! Why loop???
The smartest part of him ran down his Mama's leg when it saw the DNA dad was contributing!
Don't know who is the culprit, and if you happen to see this, I am pissed. I am working on Saturday because you can't check your code or you lied on your resume to get this job, as you are not qualified! Fuck you!15 -
Isn't it lovely when someone wants feature X and Y and one is five minutes (and mostly CSS) and the other one is hundreds of hours of backend code.
"I don't want to know, just make it happen. Jeez how hard can it be, it's just a new button"4 -
never before have I been happy to be asked to work overtime, but for once, fuck yeah...
Bit of back story, I am tech lead on a massive project that has been run like a complete shit show, the PM who also happens to be the brains behind the project seems to think we are miracle workers and for the first 9/10 months of the project would make significant, like delete a weeks worth of code and start over changes, 3-5 times per week. There are features for the v1 release that have been built in excess of 5 times. I have been saying since October that even without all his constant changes, we will NOT make the deadline, and naturally as is part of my job I argued against every unnecessary feature he tried to implement, eventually he pulled me into a meeting to tell me how much he values my opinion, I need to stop arguing with him and he does not want to work with yes men (I have a rant about that convo already).
I believe our CEO finally started smelling a rat as he insisted on joining our daily stand-ups, during which said PM scripted some lovely stories to disguise the fuckup we are in, and since has assigned another PM to take over and do proper project management and risk analysis.
That is where the email comes in, a lot of the work assigned to me will miss the deadline by a month, honestly I am impressed that it is by so little and so few people will not be missing it, but anyway, he probably spun a few stories there too.
So I spent part of the work compiling the most perfect surgical response as not not actively throw him under the bu, but create a quite a few questions that they hopefully as, as himself and the CEO where cc'd into the mail.
And the jist is, the deadline itself was still impossible and 8 of the 10 tasks assigned to be have ZERO back-end whatsoever, and those tasks are about 80/90% integration to said non-existent back-end, some of those services and data structures have not even been planned yet and we are a week past the deadline and 3 weeks from the just as useless extension. -
So another rant inspired me.
Tell me one fact or detail about your favorite programming language, other devs not using it, might not know about.
I go with: In Delphi you don't have garbage collection, unless you use interfaces the right way.7 -
Who doesn't love customer support?
So anyway, I'm the point-of-contact at our company for a specific tool we use, sold by an external vendor, whose yearly licenses cost five-digits per user. I've been the point of contact for around three years now, and most of the time it's people way more senior than me asking for help with [specific edge case] and I send them on their way with the solution. Sometimes that isn't the case though, and I need to send an email off to [vendor]'s support team.
Good support is lovely. Our go-to guy on their support team was great. Timely responses, thorough, and always willing to dig to the bottom of the case. Sometimes it's us being stupid and not knowing what the [obscure feature] toggle does, sometimes it's just a mis-match between what we're trying to do and how the tool was designed, and sometimes it's a sneaky, devious bug in their product. I still remember the pride I felt when we got an email notification for the latest release of the tool that contained a bugfix that I had gone over with their dev team on call to figure out how to reproduce.
However, just over a year ago they changed our go-to guy. It started off small. The new guy was more terse in his responses. Less attentive to the little details in the message. Gather as much information as possible first, deal with the actual problem we were having second. He'd fix the immediate problem, but more open-ended questions about best practices to avoid another mess in the future would be ignored.
But slowly it got worse. Less responsive. Entire paragraphs of context would be ignored and had to be repeated to him. More generic responses. The odd case got dropped entirely. Last time I opened a support ticket, when I asked for additional clarification I got a ChatGPT-ass response only tangentially related to the actual context of my question (you could tell it was copy-pasted because he didn't even bother to paste without formatting).
Now upper management is unhappy with [tool] and are on my ass to get them to solve all our problems with it. What does new support guy reply with to my ticket with clearly bulleted questions, written in bold to separate them for clarity from the surrounding context? A two-line, nonspecific request for information entirely unrelated to the issue at hand, to the point that me and everybody from my company in cc privately went "why the fuck would we even send that??".
These next few weeks are going to be fucking rough, dear god may this be over soon.1