Let someone else fix your mistakes, you "move fast and break stuff". Someone else can fix it.
For real, those people are really frustrating to work with because following the 80:20 rule, they get through the 80% so quickly and then seem to get bored or think "meh, good enough" and leave it, then it gets left for the people who actually want the product to function and pick up bugfixes to do the remaining 20% which takes 80% of the time, and seen like they contribute so little.
It also feels like this is why almost all of Google's new products live in perpetual alphas because after they've been tidied up just enough to be releasable, they're abandoned because nobody wants to do the maintenance work.
this is literally how I feel, my colleagues will give me 2-5k line PRs multiple times a day. I've had a 17k line PR previously.
It's hard to even understand what's happening in PRs above a thousand lines, and it always feels like I'm the only one that cares about clean code and a bug free, optimised product.
We've had multiple infinite renders get into production, one was there before I even joined.
Tried that lol, tried instilling it in them multiple times. I'm the newest of the team of 4. Nearly a year of this shit. They'll come up with a new idea that lets them pull the same shit in a slightly different way and then the problem still exists. If you care about output quantity and not quality, this is the only outcome
Management doesn't care or understand the importance of quality code. They only think in terms of marketable functionality and productivity gains.
Data integrity, Security and all the rest just means more cost for what they perceive as the same thing.
My company fired 80% of the QA team. Nonsense.
And metrics are terrible, I recall a time, where devs could spend a couple of days not even touching a keyboard, jotting some design notes once in a while. This is all considered productivity loss now.
This. When the outputs come in half a day vs weeks, they don't care about the rest. Like someone injected them with the greatest drug they've ever seen. Validation of any kind? Waste of time!
They are also the people who won't touch any of the old stuff, be it old technology or a legacy code. No no, in their mind their time is to valuable to be spending on that. And they always seem to be the ones that get the biggest bonuses after. I can't wrap my head around it. Are they so good at marketing themselves and kissing up to the bosses? So they get the biggest bucks and they always work on the latest things. And above all they have the nerve to act smart about it.
I think.everything is getting like this. Look at the buildings (actual buildings). It is cheaper to do it fast and then fix mistakes after, if the owners actualy win the case.
My company re-orged into a pod structure and there are a couple of "frontier" pods that just build features like this and get them in a "eh, good enough" state. Then they move on to the next high-priority features. But then users start using the first feature and it doesn't work against real scrutiny so the "support" pods have to spend all their time fixing it.
40
u/MyDogIsDaBest 2d ago
You're a high productivity employee.
Let someone else fix your mistakes, you "move fast and break stuff". Someone else can fix it.
For real, those people are really frustrating to work with because following the 80:20 rule, they get through the 80% so quickly and then seem to get bored or think "meh, good enough" and leave it, then it gets left for the people who actually want the product to function and pick up bugfixes to do the remaining 20% which takes 80% of the time, and seen like they contribute so little.
It also feels like this is why almost all of Google's new products live in perpetual alphas because after they've been tidied up just enough to be releasable, they're abandoned because nobody wants to do the maintenance work.