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
-
Deciphering 10-20 jira tickets that relate to 1 feature which aren't linked in anyway beyond titles spread throughout an epic or 2.
Ah the pain of having to go through 200 tickets to find everything you need for a single feature.7 -
Arguing over PRs with juniors who try to push unnecessary badly maintained dependencies, which are in fact just turds wrapped in startup hypespeak, because they're too lazy to actually invent some non-square wheels.
-
Explaining to my boss why we can't use the WordPress theme he saw on Theme Forest in an Android app7
-
Tracking my time. I always forget to do it while I’m working and end up having to bullshit it at the end of the month. And then it takes like two hours to finish. 🤮8
-
Meetings, responding to emails, handling urgent tickets, etc. If I could just get four uninterrupted hours of coding in a day, I'd be happy. But I'm basically in meetings all morning and usually have at least 1 more in the middle of the afternoon.2
-
I can't sleep whenever I remember ,few year before I paid $25 for ethical hacking workshop and they show us inspect element n SQL map
-
Doing GUI agile testing with the QA before passing my code to test server. I do this 'cause the QA marked in the past a lot of bugs that aren't bugs because he didn't liked the wording (in spanish there's A LOT of ways to say the same thing), the color of a button or an icon, and this delayed the release of the code a lot of times. So, this way I can change things to avoid unnecessary bugs... if the QA is not so busy XD
-
I really hate it when I work on a user story consisting only of a cryptic title: "Implement feature X".
Esp. when I missed planning during a holiday and can only wonder who in their right mind would have given it 3 points.
Why thank you.
Sometimes, just pulling the acceptance criteria out of somebody's nose takes days. It doesn't get better once I realize that not all external dependencies have been properly resolved. It's worse if there are other departments involved, as then you get into politics.
Me: "We are dependent on team X to deliver Y before we should have even planned this ticket. I'm amazed that our team was even able to estimate this ticket as I would have only raised a question mark during estimation meeting. We could have thrown dices during estimation as the number would have been as meaningful and I'd have more time to actually figure out what we should be doing."
Dev lead / PO: "I understand. But let's just do <crazy workaround that will be live until hell freezes over> temporarily."
It's borderline insane how much a chaotic work flow is branded as agile. Let's call it scrum but let's get rid of all the meaningful artefacts that make it scrum.1 -
When I have to updates the apps for the second company of my boss:
5 apps, 4 different projects, 4 stores.
Each app with different VR SDK, which makes the differences minimal, but still can't merge the projects.
It takes about 1h to build all of the apps (like 30m just for the iOS ones), 5minutes to 5 days to make the edits, 1-2 weeks of debugging and testing, plus the time the stores take to actually publish the apps
Always makes me wanna kill myself -
Doing like Penelope, adding crazy features commissioned by our boss and removing them the day after 'cause they're useless and "that's not what the client wants". Boss, let us finish this fucking shroud, so that we can bury you with it!!
-
Anything that I can make a computer do but can't because my boss doesn't think it's a good use of my time...
I have a lot of those now but can't automate them because.... I'm too busy dealing with them...4 -
Worst busywork?
Having a graphic designer on the team that doesn't know development.
Gods, the amount of tweaks and adjustments they come up with.5 -
Thankfully not anymore, but Asana was the most frustrating and confusing piece of crap when I had to work with it.
I would literally spend hours trying to sort out where everything came from, let my boss know that other people were trying to get me to do something via some private task that no one else can see, sort out random ass replies to random points in conversations and then open up my email and answer all the half-baked open ended questions that were sent separately over email.1 -
When I need to ask my boss something...
Jesus... This guy explains you 3 HOURS long on why you need this cable and why you cant use another one, and he wants you to write it down... Every. Single. Word...3 -
Having to relieve 50% of my boss' workload in DevOps. I'm 10% in, I don't know how this guy is still mentally sane.1
-
Right now, everything. I started at a Consulting firm because I expected many new problems to tackle, solutions to develop and generally to always have a fire burning underneath my ass but instead I always develop the same standard bullshit.
I miss the days in my old job when there was just a problem and the task to solve it. When I stared down giant amounts of data, just KNOWING that somewhere in that mess is some structure I could exploit and that short moment of inspiration when I finally pinpointed it. The rush of endorphins when the solution became clear and everything fell into place to form a beautiful pattern amidst the chaos test data, git commits and numpy arrays.
Now its just "Yeah, would you just write another selenium testsuite that throws out fail or pass and wastes all the information because the only reason I'm a testmanager is because I'm too incompetent to do anything else and not my passion for the field".
The constant, mind numbing repetition of always the same patterns where the occasional dynamic element that becomes stale is the highlight of my work week... I would have never thought that making good money with easy work would ever get me as close to depression as it did.5 -
R&D while I wait for management to decide on clear direction for the next project and then waiting for the designers to create it.
-
Pulling reports that never get used for anything.
Even when something does go wrong, that means going and pulling fresh data instead of referencing the reports on seemingly niche stuff to get sent off to exec who are 100% in too many pointless meetings to ever read the damn things5
Top Tags
Weekly Rant
View