Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "wk183"
My former job. Imagine hiring consultants, hiring the best dev team, then bypassing the consultants and then breathing down our necks how to do our jobs:
"We need six day workweeks because more days means more work done."
"We need to enforce a 9 AM schedule for all developers so that the other departments won't feel jealous of the devs."
"We need this feature done stat, alongside the existing feature that you guys are doing for that sprint. No if I had to tell the product owner and the Scrum master about it, we would get nothing done."
"Why is the QA uncovering a lot of bugs! Guys this is shameful! You're costing the reputation of this company!"
"You need to deploy that on or before Friday? Do you understand? No it can't be done in two weeks. I already promised my investors that it will be done Friday."
"See you guys later in Slack while we deploy X to server at Monday midnight. And yall still come over at 9 AM."
"You need to implement this feature we thought of while we were drunk last night. No I hadn't told the product owner yet."
"The back-end dev isn't supposed to have access to the production server." Then weeks later scolds the back-end dev, "What is wrong with you? Why do you have no clue what's going on in the production server!"
"Okay let's use this expensive API over the cheaper alternatives." Then weeks later "What have you guys done! Why do we have a ten grand bill from the API guys!"
*orders the QA around, becomes their errand boy, etc then lets go of the QA* "You're doing a poor job being QA."
I can cite moooore examples.10
I'm not sure if this entirely qualifies and I might have ranted about it a few years ago but fuck it.
My last internship. Company was awesome and my mentor/technical manager got along very well with me to the point that he often asked me to help out with Linux based stuff (he preferred Linux but was a C# guy and wasn't as familiar with it as me (Linux)).
We had to build an internal site thingy (don't remember what it was) and we delivered (me and some interns) and then the publishing moment came so I went to out project manager (a not-as-technical one) and asked if he could install a LetsEncrypt certificate on the site (he knew how and was one of the only ones who had direct access to the server).
He just stared at us and asked why the fuck we needed that since it was an internal thing anyways.
I kindly told that since it's free and can secure the connection, I preferred that and since its more secure, why the fuck not?
He wasn't convinced so it was off.
Next day I came in early and asked my mentor if he could do the SSL since he usually had access to that stuff. He stared at me with "what?" eyes and I explained what the PM said.
Then he immediately ssh'd in and got the damn cert with "we're going to go secure by default, of course!"
A minute later it was all set.2
Our boss decided that a new guy joins our team now, as we are under pressure to finish a product. There are 2 sprints left for that. Afterwards, we'd have all the time in the world to onboard him properly and getting him familiar with our system. But no, le boss said he'd start now, so he does. We're losing focus and time better spent on the product. And the new guy isn't feeling useful either, because he has no idea what we built so far.
Don't get me wrong, the new guy seems like a good addition, in general. But that timing is awful.10
I feel quite stupid asking this but what on earth is eng in English? In dutch it means scary but I don't think that that applies here 😄
(Translation services gave me the exact same word)12
"Disregard what you're doing now. We need a FUNCTIONAL prototype (which will become the main app because refactoring is a waste of time huehuehuehue) with these features our POSSIBLE client MIGHT potentially need for TOMORROW's presentation."
"What do you mean that thing you were working on yesterday isn't done? Those are the times we estimated, right? By the way, our (still not confirmed) client thinks he'll choose us over that other company if we do changes A, B, C and D. Need it for yesterday."2
The development department got an order to remove certain functionality from our current server monitoring solution, so that we had to use a new, still very in development solution, that is full of bugs and super unreliable.
End result? We now have to have two windows open all the time, while also hoping the new solution actually works, as it tends to stop refreshing randomly, and tends to give false positives a lot.
I can't believe this shit happened in time for this week's rant!
Here it goes.
I have a table on AWS Athena which has partitions. Now, in the earlier versions of this project whenever I write something to a new partition a simple `MSCK` query worked (and keep in mind I am NOT deleting anything)!
Now, my so called Team Lead in the PR for the latest (major) release tells me to change it to an `ALTER TABLE`. I was like fine, but I did not add the s3 location to it, because it was NOT NEEDED. TL asks me to add location as well. I try to convince this person that it's not needed, but I lose. So there it is in production, all wrong.
Today I notice that the table is all fucked up. I bring this up in the stand up. The main boss asks me to look into it, which I do. Figure out what the issue is. This TL looks at it and says you need to change the location. I put my foot down.
"NO. What I need is to remove the bloody location. IT'S NOT NEEDED!"
TL's like, "Okay. Go ahead"
1. It's your fault that there's this problem in production.
2. Why the fuck are you looking into this when I was clearly told to do so? It's not like you have nothing to do!1
Confirmation message takes too long, ask us to make it faster as it should not hold the user back.
Next week: the confirmation message is too fast we must please make it slower 🙈2
I start programing in 8th grade as hobby, write games. I got job in just 50$ a month.
The part is, I work 3 years in same.
Now after 13 years of work I got a job here in my current company, where we developers got our desired respect. I can say a good sallery too.
But I think sallery doesn't matter mucch, if your bosses are not nuts and they can understand the problems of developers.