Details
-
SkillsPerl, Javascript, PHP
-
LocationGermany
Joined devRant on 11/14/2017
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
-
Well, I was the One that was scolded. Because I basically took over without asking permission to fix a critical outage.
I fixed it within 3 minute, while the person in question have been trying for 2 hours.
He then got very angry and told me infront of everyone that "dont ever help me out".
Said and done. I never helped him ever since, even if he clearly struggled with everything.
He got fired recently due to incompetense6 -
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.
And later:
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.
And later:
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.
And later:
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.
*twitchy smile*rant useless people you suck because we are incompetent what's a query log? it's all your fault this is super urgent let's defer it ticket notes too long; didn't read21 -
I lost my job 😅 tbh did me a favour. I was backend, this guy was frontend and was a typical opinionated JavaScript, magpie dev and I just did not give 2 fucks about what he thought was “amazballs” and we had a small tiff, we’ll he was arguing, I was trying to do my job and I just didn’t care enough about his feelings on the subject, forget what it was about but I think it was trivial. But anyway, I was let go soon after 😅16
-
PSA:
Next time you plan on changing all your model names from "xxxxx" to "xxxxxModel", under a minor version bump so that everyones CI breaks, in order to deliver no benefit whatsoever ..... don't8 -
we need you to fix this bug that cannot be reproduced
ugh so now i have to go figure out how to reproduce it? i dont think this shit is even priority4 -
Shit went very well - I am really happy for my future
Hopefully, the bureaucracy will be faster for me :P
Details? Not yet5 -
Recruiter: Your skills are amazing! There's hight demand! massive shortage! the market is hot!
Me: great
Recruiter: But your rate is too high.
Me: ....7 -
Messaging me at 4:30pm on a Friday about a high priority issue currently in production.
My reply: a link to the code review from 2 months ago that literally explained the problem and what to do to fix it. That got implemented. Then removed. For some reason...
Feels good.2 -
I currently work on a legacy system for a company. The system is really old - and although I was hired as a programmer, my job is pretty much glorified data entry. To summarise, I get a bunch of requirements, which is literally just lots of data for each month on spreadsheets and I have to configure the system to make it work, which is basically just writing a whole bunch of SQL scripts.
It’s not quite as simple as that, because whoever wrote the system originally really wrote it backwards, and in fact, the analysts who create the spreadsheets actually spend a fair bit of time verifying my work because the process is so tedious that it’s easy to make a mistake.
As you can guess, it is pretty much the most boring job ever. However, it’s a full time job with decent pay, and I work remotely so I can stay home with my son.
So I’ve been doing it for about 18 months and in that time, I’ve basically figured out all the traps to the point where I’ve actually written a program which for the past 6 months has been just doing the whole thing for me. So what used to take the last guy like a month, now takes maybe 10 minutes to clean the spreadsheet and run it through the program.
Now the problem is, do I tell them? If I tell them, they will probably just take the program and get rid of me. This isn’t like a company with tons of IT work - they have a legacy system where they keep all their customer data since forever, and they just need someone to maintain it. At the same time, it doesn’t feel like I’m doing the right thing. I mean, right now, once I get the specs, I run it through my program - then every week or so, I tell them I’ve completed some part of it and get them to test it. I even insert a few bugs here and there to make it look like it’s been generated by a human.
There might be amendments to the spec and corresponding though email etc, but overall, I spend probably 1-2 hours per week on my job for which I am getting a full time wage.
I really enjoy the free time but would it be unethical to continue with this arrangement without mentioning anything? It’s not like I’m cheating the company. The company has never indicated they’re dissatisfied with my performance and in fact, are getting exactly what they want from employing me.5 -
Man do I love receiving bug reports and comments in Turkish, Russian, Portuguese or Iranian. I should really just start replying to those in Polish.
I added a humorous pinned post saying “By the way, I can only reply to you either in English, Polish or Dutch :)” to the program where I receive such reports.
I am aware it won’t do jackshit, because people can’t read.
Kurwa.10 -
You know that you life has gone to shit when you type "p" into your browser and the first thing that comes up is "postresql"2
-
Do you know what's better than getting work done. HAVING ANOTHER F****ING MEETING ABOUT WHAT WORK NEEDS TO BE DONE!
I COULD'VE HAD MOST OF THIS SHIT DONE BY NOW BUT I HAVE TO SPEND 1/2 OF EVERY DAY JUST EXPLAINING WHAT THE F***K I'M DOING, WHAT THE F**K EVERYONE ELSE IS DOING, AND THEN EXPLAINING WHY IT HASN"T BEEN F***ING DONE!
YOU WANT TO KNOW WHY EVERYONE IS LEAVING WHY YOU CAN'T RETAIN ANYONE? YOU HIRED THEM AS FREAKING ENGINEERS PROMISING THEM THEY WOULD BE ABLE TO DO THINGS AND THEY SPEND ALL DAY IN F***ING MEETINGS WASTING THEIR IQ AND WISHING FOR DEATH!
GGAAAHHHHH! BY THE EMPEROR PLEASE COMMISSAR END ME!4 -
Remember the super duper company I applied for? (Last rant)
Well, I did their coding challenge. And after many years I had to do a metric crapton of C++. It's not a fun language. It's frustrating how human-unfriendly it is, and maybe one reason why I low-key like it.
Anyways, here's hoping that I didn't fuck up too much.
On a side note, I realized tensorflow actually has a cpp api. I think I'm gonna work with that in my next mental breakdown. 🧐7 -
My bosses, bosses, boss asked to call me up unexpectedly:
BBBoss:" Just wanted to say we are really happy with your performance, especially in these tough circumstances, ... "
Me thinking: "Ah, great I am getting laid off."
BBBoss: " ... which is why we decided to give you and extra 1000$ in you next paycheck."
Me: "??? ... for real."
BBBoss: "yes, thank you for your hard work."
Me: "I am still employed?"
BBBoss (laughs) :"Yes, we are happy to have you."8 -
I am back with some more emotional shit.
So tomorrow is my last working day at my second employer where essentially I'll just walk into the 10 seater serviced office to drop my laptop in a cupboard because no one else is here.
So today, an hour ago, they had a virtual farewell for me and everyone spoke of me highly with specific examples.
Well that's not what this post is about, but the emphasis is that I am still in dual mind of whether I made the right decision to quit my second employer so soon (in just 10 months)?
If I had stayed for two months more:
1. I'd gotten a hike this week
2. More RSUs in that hike along with cash
3. Joining RSUs would have vested for the cliff period of 1 year
4. Tenure would be at least a year
5. Would have found a better job with higher pay (on the new hiked salary).
I surprisingly got the grip of the product and that's when I decided to quit.
The reason I quit is I wanted to optimise for WLB and timezone with better team culture.
While the next job is surely a company I wanted for a long time and that too in B2C space, I really lost my affection for that role and that's where it came to me upfront and I rejected them initially before picking up the offer again.
My second employer is a very global and one of the largest brands. Really wanted to stick around and never got to enjoy the benefits which others did.
Only time can tell, because when I chased something I never got it, when I stopped, it came to me.
And what I am chasing now is something I am unable to achieve.
Why is life so fucked. Seems like I am about to lose one of my biggest and only life and career dream.
Maybe I fucked up this decision. Maybe not. Only time can tell.12 -
Dev: What do you think of the new version of the app?
Client: It’s great! We just have a couple notes of feedback we are working on compiling. We should have those to you by next week.
*Next week*
Client: We need another week to compile all of this feed back we are generating
*Another week goes by*
Client: Still working on it, it’s going to be a really thorough review when you get it though. No stone will be left unturned!
*2 weeks later*
Client: Here it is!
Attached: A word document with a single line of text “can’t nobody log in” next to a picture of the login screen with a red circle drawn around the login button
Client: Can you hurry up and action our feedback? We want to go live next week
Dev: …9 -
Best co-worker quitting story?
"T" I've refereed to in previous rants knew he was close to being fired, so he jumped ship. 'T' sent the usual "I'll miss you guys" email to the department, except me (and a few others that didn't fall for his BS and not scared of him). His mistake was he sent the email out a day early (buddy forwarded me the email) and left the stuff (box of pics, books, etc) he planned on taking with him. One item in particular was a new company provided laptop bag, which technically wasn't his to keep (supposed to leave/turn-in any company provided equipment), so I grabbed the bag and hid it.
The next day I heard him slamming drawers (looking for the bag) and a loud cursing. Other devs peeking over the walls asking what's wrong.
Dev1: "Dude, what's up? Whatcha' looking for?"
T: "Nothing...fuck!...damn it...nothing...assholes...fucking assholes!"
Dev2: "Who's the ass? What's wrong?"
Dev3: "Need help looking for something?"
T: "No..no...nothing...I'm fine...making sure I don't forget anything."
'T' never found out who took the bag and I've had that laptop bag underneath my desk ever since.5 -
When you ask for documentation and they hand you a Word document with screenshots of the changed code4
-
Nothing screams panic like accidentally deploying an older, broken staging build, that also run outdated database migrations on start, straight to production3
-
I've told this one before, but the guy had his platform bought with a promise of partnership. they kept stalling the contract, and he would repeatedly ask when he was gonna get paid his share, and eventually they said "we never promised that". he deleted everything from the team's computers, revoked all access and left. since there was never a contract, they didn't do anything about it5
-
I just applied for one of those big big biiiiiiiig companies in robotics...
Something in my mind is telling me that I am actually losing it. Like, my mind. I must be losing my mind. 🤔
Oh well! ¯\_(ツ)_/¯26 -
Oh my god my brain is hard wired to write c++ in snake case. Spent 4 years doing it. This code base uses camel case.9