Them: Root, you take too long to get tickets out. You only have a few simple ones. You really need to rebuild your reputation.

Also them: Hey, could you revisit this ticket? Could you help ____ with this other ticket? Hey Root, how do you do this? Root, someone had a suggestion on one of your tickets; could you implement that by EoD? Hey Root, i didn't read your ticket notes; how do you test it? Hey, could you revisit this ticket for the fourth time and remove some whitespace? Hey Root, someone has non-blocking code review comments you need to address before we can release the ticket. Hey Root, we want to expand that ticket scope by 5-6 times; still labeled a trivial feature though.

Also them: Super easy ticket for you. Make sure you talk with teams A, B, C, D, E and get their input on the ticket, talk with ____ and ____ and ____ about it, find a solution that makes them all happy and solves the problem too, then be sure to demo it with everyone afterward. Super easy; shouldn't take you more than a couple days. Oh, and half of them are on vacation.

Also them: Hey, that high-priority ticket you finished months ago that we ignored? Yeah, you need to rewrite it by tomorrow. Also, you need to demo it with our guy in India, who's also on vacation. Yes, tomorrow is the last day. (The next day:) You rewrote it, but weren't able to schedule the demo? Now you've missed the release! It's even later! This reflects very poorly on you.

Also them: Perfect is the enemy of good; be more like the seniors who release partially-broken code quickly.

Also them: Here's an non-trivial extreme edgecase you might not have covered. Oh, it would have taken too much time and that's why you didn't do it? Jeez, how can you release such incomplete code?

Also them: Yeah, that ticket sat in code review for five months because we didn't know it was high-priority, despite you telling us. It's still kinda your fault, though.

Also them: You need to analyze traffic data to find patterns and figure out why this problem is happening. I know you pushed the fix for it 8 months ago, and I said it was really solid, but the code is too complex so I won't release it. Yeah I know it's just a debounce with status polling and retrying. Too complex for me to understand. Figure out what the problem is, see if another company has this same problem, and how they fixed it.

-------------

Yep. I'm so terrible for not getting these tickets out, like wow. Worst dev ever. Much shame.

LF work, PST.

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?

Thanks

[LinkedIn, Recruiter InMail]

Hello,

I am Lazy As Fuck, and I'm looking for people to work for a company that pays me for doing nothing.

Do you know anyone that is an Angular developer? If you do, please tell them to send me their resume and phone number.

Thanks.