upvote
> I've worked with people who consider themselves 'prolific humans'. Someone always has to tidy upp later, and its never them

I run both infrastructure and security - that means a lot of relatively self-contained PRs to infrastructure-as-code and dependency management systems. I'm also the team lead, which makes me responsible for a lot of throwaway prototyping, as well as cleaning up anyone else's mess...

Yes, the prolific-but-damaging engineers are all too common in corporate. But particularly in startup land, you tend to find your high-performers wearing a lot of hats at once.

reply
My experience is that it's even worse: they've already produced enough code that the codebase matches their taste and theirs alone.

So in essence you have one guy working at 4x and e.g. four other getting just 0.7x - net effect is still positive, but everyone save for that one person is miserable.

Mind you, the 4x dev doesn't necessarily have to be particularly talented - they only need to get their foot in the door before anyone else.

Back during the ZIRP days you could immediately tell that this is the case in a team by staff rotation alone. Nowadays people understandably cling to their jobs, so you might now know until it's too late.

reply
> … and its never them

IME, it’s because they lack the experience to have the Taste one develops as a senior engineer. “This works, and is somewhat understandable” is as far as they get. Little to no understanding of how this solution could fit better in the codebase.

reply
There's also those that burn themselves out, and John Carmack!
reply
That's such bullshit.

I've managed some incredibly prolific developers and some very slow ones, and the prolific ones are pretty much always the ones more available, more willing to fix things, more willing to take feedback.

And also: they make less mistakes because their skills are sharp. This anecdote comes to mind: https://austinkleon.com/2020/12/10/quantity-leads-to-quality...

If you have to constantly rationalize performance differences by demeaning others, this says more about you than the prolific people.

reply
I've worked with both types. Some prolific devs really do care, and are just really good at their job.

Others are just trying to get code done, and don't care about quality. These are the types that are upset that their code gets rejected because their goal is advancement and money, and not doing a good job.

FWIW, it's okay to care about both. But if you don't care about doing a good job, you're going to drive everyone around you insane.

Prolific bad coders are a bane on the company, and AI is only going to make them worse.

reply
Sure but if PRs get rejected, nobody has to "tidy upp (sic) later".

That's not prolific, that's just producing slop, with AI otherwise.

I'm just tired of developers pretending that low output is some sort of silver bullet for quality, and high-output is automatic slop. Neither are true. In 99% of cases, low output doesn't correlate with anything positive. High-output can naturally go either way, but slop doesn't make one "prolific".

reply