6 ms·
The actual issue is not the "bad" engineers but the bad organization. While people are allowed to push and merge whatever crap is generated there is no point to
by ponector 1mo ago
The actual issue is not the "bad" engineers but the bad organization. While people are allowed to push and merge whatever crap is generated there is no point to do otherwise. Even if you do care about performance, "good" code your teammates don't and close more tickets and are better by many metrics.
If you are closing one ticket per week with "good" code but your teammate does three with "bad" code - it's actually you are a bad employee. Also they may say you are a toxic one.
- florianherrengt 1mo agoIt means the company is measuring the wrong thing. I would much rather have someone on my team who ships less but whose work I can trust than someone much faster whose changes leave me wondering what problems we’re going to discover later. And when production breaks (and it will), I need the person who made the change to actually understand it well enough to help fix it, instead of showing up with no idea what is going on. You can obviously be an asshole about how you do it but I don’t think pushing back makes someone toxic. You need to be flexible and compromise when the business trade-off makes sense. But you also need a backbone. If you think something is going to cause real problems, bringing it up is part of the job.
- ponector 1mo ago>>I would much rather have someone on my team who ships less but whose work I can trust Me too, but it is not what happening across the industry. Instead they are pushing for more LLM usage as well as more features. And faster, faster!