Details
-
SkillsPython, C++, AWS, Docker, Linux, free bsd, networking, circuit design, hacking
-
Website
-
Github
Joined devRant on 5/27/2021
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
-
Let's get ready for another rant. I work at a new company now which claims to be "fast paced" and startup-like culture. At the same time, I don't think I've ever seen a place with more rules and bureaucracy when it comes to engineering.
By the looks of it, my manager seems to value process a lot more than actual outcome. Both my manager and another engineer in the team tend to nitpick over every line of code and will not approve anything until they believe it's absolutely perfect and up to their liking.
Every PR I create has to go through 5 cycles of review. On top of that, the comments that get added are rarely related to product impact, but rateher "let's rename this variable in a test file to this", "maybe we should have this many spaces in a config file". There's been actual cases where I had to go through different cycles and had my PR's blocked for days because of some minor comments about variable names and styling they "liked" more.
This is one of the main reasons why we lose critical time during the development of our features. There seems to be no sense of priorities or urgency. The other reason we keep losing time is because of the massive amount of team meetings we have. Our team has only 3 engineers. How many meetings can you possibly schedule in a day to "realign". We have technical meetings where it apparentely is necessary to all agree on every tiny detail, such as which types we're gonna use etc etc.
That's not all. Last week, weeks of my work was thrown out of the window, because it was slightly different from how "we" usually do it. Even though, I explained and motivated how my solution solved issues the other proposed solution did not, we ended up spending an additional two days reimplementing the same fixes more in line with "the rules".
I recently reviewed a coworker's PR pointing out actual functionality that was not working as expected. Real user impact...
I created an alternative solution that covered all cases, and sent it. It got basically ignored. Then we ended up having a meeting for hours with several engineers where they made me watch how they started fixing the same issues as I had already fixed.
Each week, I'm losing around 2-3 days of development time dealing with this nonsense. But then there's a deadline. Then the manager goes full-on wild and pushes everyone into overtime and will send you 700 messages a day in channels or privately to you if "you need help" and how things should be done.
I'm not looking forward to switching jobs again, but please tell me... how can I cope with this?
Thanks3 -
YOU KNOW WHAT I AM DONE WITH PR REVIEWS , LIKE WHY DO THEY EVEN EXIST THOSE mf's dont know anything aboutT how much I HAVE worked on MY CODE FOR THEM TO SAY can you make this function more descriptive bro its fucking getuserinput Wth do you want it like(GETUSERSSHITFROMTHEIR..nvm)Screw you Grammarly
AFTER their stinky a doble ss stops commenting LITERally I have made phaking changes in half of the CODE and what do I receive "LGTM" you m.. you look like you belong the african Sh..LGBTQ community YOU look LIKE YOU NEED SOME EVOLUTIONARY GLOWUP , STOP MAKING MY LIFE HELL, next PR I am merging it straight INTO his A double S , Love you grammarly5 -
🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡5
-
Finally fixed that bug after hours of debugging, and a bit of crying/screaming… and now I have a brand-new error message to cry about. Progress I guess?1
-
How the fuck did the engineers at Tiktok pull off the American 'ban' so seamlessly. Take it down and then put it back with little loss to functionality.
How do you think they accomplished that with so many accounts.
Anyone works there can comment?9 -
By the time you get to need to learn Kubernetes, people are usually too far deep in their engineering careers and already have this 'not even more shit' fatigue.4
-
I've been using Void Linux on servers for years. I decided to finally contribute some packages, and wrote a tool to make it easier to build packages outside of the standard repository. This post covers some useful tools in Void, my voidup package building tool, and many of the issues I encountered which make me wonder if I should keep support Void Linux.
https://battlepenguin.com/tech/...1 -
Not remembering something isn’t an indicator that you are busy, it just proves u have bad memory and poor management skills.
-
Today issah is born to tell us to fucking love each other so dont be a bad bitch today or you're gonna get whipped by some white dude doing a blackface1
-
Is devRant Losing Its Spark?
Hey ranters,
Anyone else notice how quiet devRant has become? Back in 2016-2017, this place was buzzing with energy, but now it’s down to just 10-12 rants a week. What happened? Did competition from platforms like Reddit or Discord take over, or did devRant stop evolving?
I still believe this platform has huge potential—developers will always need a space to vent and connect. But without fresh ideas or a clear roadmap, it feels like devRant is fading.
To the creators: what’s the plan? To the community: do you feel the same? Let’s discuss!
A concerned dev.56 -
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI
We don’t need UEFI14 -
Well, the rant is because I have to go to Madrid twice a month, which is annoying.
But now I'm writing your GPU drivers, bitches 😂.
More concretely, for those who may care, gonna work in HLSL to spir-v conversion.10 -
Worse than the "working on my machine".
Meet the "works on every machine but the boss laptop".
Bonus point if the issue appeared out of the blue during the night.2 -
Me: Hey, guys, this stuff is seriously flammable. Like, I’m surprised it hasn’t caught fire yet. I really want to clean it up. Here’s how I’d make it better.
Management: No. It’s fine, it works. Don’t touch it. It’s getting replaced anyway. Just add the things on top like we asked you to, and call it a day.
Me: Are you sure? This is seriously going to be a problem.
Management: We just said it’s getting replaced. Don’t. touch. anything. OK?
Me: alright.
… Eight weeks later …
Management: so this thing caught fire over the weekend, and the fire spread to other areas. We’re doing some emergency cleanup. The new guy looked at it and figured out why, and has some great ideas on fixing it, so give him some well-deserved praise!
Me: Hey! I told you about this months ago!
Management: Yes. I tuned out during today’s firefighting meetings. But it’s important to strike a balance in everyone’s style. Do you have any other concerns?10 -
My daily standup currently is an hour long debugging session what happened to our servers... Idk why I'm even present since I'm just a frontend dev that does 0 work on this product.3
-
Open letter to any website that is trying to implement "smooth scrolling" on their website using JavaScript: stop, consider how awful it is 100% of the time, and kill yourself please.1
-
I did it.
I finally fucked prod.
And had to do open heart surgery on the service to get it unfucked.
Shit happens. Luckily its internal prod only...9 -
No one fucking knows how to handle/raise errors.
I feel like this is the least talked topic in all fucking programming industry. This shit needs to be tought even more than the fucking SOLID, DRY, KISS, YAGNI and other kinds of buzzwords that fancy devs love tossing left and right.
Basically everyone just does "whatever you dumb error just dont bother me". They will just log/return null/ignore the errors and be in their oblivion with bugs propagating upstream the call stack.
"Throwing errors you say? Ew, why do you want to produce more errors?". Yeah, right, just stick another log/return null/or ignore the fact that the monke calling your function with bullshit arguments.
"But bro it's so difficult and time consuming and it would never happen!" Yes, you fucker! Yes! Programming IS fucking difficult if you want reliable systems! Did you not know that!? Well now you do! Go and fucking learn it!
FUCK!11!1!!25 -
No raise. Not like I single handedly rewrote one of our weirdest and most complex legacy code bases or anything... Oh and even so they whined about how long that took that's probably reason they'll cite if I ask about this lack of raise thing.
I mean, technically I got a little more just because the tax rates are different for the new financial year but come on5 -
Week : 50
How is the weekend going?
Which is your favorite color? Why?
Previous Week : https://devrant.com/rants/109409478