You must log in or register to comment.
I’ve seen this claim recently and it’s rubbish.
Yes, if by “nothing” we mean writing next to no code, because they’re busy either:
- architecting software solutions, as they’re knowledgeable enough that they should be doing this instead of writing code
- understanding a lot of what is going on in components and/or the system so that when there’s an issue they say “oh, this is likely because of X” and the resolution takes days instead of weeks.
I.e. yes, there is a percentage of developers who we pile other tasks on and they don’t get to write code.
My experience is that the more knowledgeable developers get, the less code they write.
Then neurodivergent peeps are different - an Autistic dev might be super knowledgeable and happy writing unit tests because they don’t enjoy the uncertainty of large problems, or an ADHD developer might have a large system-wide view but write what seem like small contributions.
It’s possible to have a developer that does nothing. But that’ll requires a project manager that does nothing and a manager that does nothing. And coworkers that are willing to put up with that shit. Everybody’s running kanban or agile simply to keep this from happening.
Actually watch the video, you’re way too generous in your analysis.
The metric is essentially lines of code. That’s it.
So everyone who isn’t hacking away ultra verbose code is considered useless. Lead devs and architects often don’t write any code at all. They’re not unproductive.
deleted by creator
Maybe our company is an odd one out but I’m pretty sure that number is more like 20-30%…
Out of a team of 10, 2 of us do about 50% of the work. 3 do about 30%, and the remaining five do about 20%… With probably two to three of them doing effectively nothing most of the time.
In our team isn’t abnormal.
