Do 10% of developers do nothing?
Do 10% of developers do nothing?
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
You're viewing a single thread.
That rate seems high. But, I have done post-mortems on a bad developer's run at a company, and found they did very nearly nothing. No commits, no issues opened or closed, some comments, but that was almost their entire digital footprint.
Most developers I've worked with are obviously not doing nothing, though some of us (including myself) get stuck doing a lot of work on a project that never makes it into production due to shifting priorities.
Yup. I'm a senior software dev, and some weeks I write no code at all. Sometimes that's because I'm researching something (output is a doc a/ estimates), other times it's code reviews, and other times I'm stuck in meetings all week.
But most weeks I'll write some code, even if it's just fixing some tech debt. If someone isn't contributing for a month, they're definitely not doing their job.
Our most critical dev / solutions expert spends most weeks in meetings.
That's our architect, and they're not a dev (they don't even do code reviews), but they are quite critical because it's their job to understand the entire app, including in-progress changes from other teams. They have their own team (architecture), so they don't report on any dev team, they report to the director.
Maybe that's what others are calling a "lead dev"?
Seems to be a trend, my boss was telling me that the VP's in our org think we need more lead devs and less solutions architects, though they would functionally be doing largely the same role, meetings, planning, design, interfacing with teams they are dependent on, annual technology reviews etc. I think it's going to bite them in the end
I imagine hiring will be an issue. Devs want to dev, and naming an architect role a "dev" role doesn't communicate the role properly.
Yep, they talked about it a bit during my hiring what I wanted my title to be since they are paid the same and do the same tasks(in addition to some coding expectations). I'm glad I chose architect, but ultimately they squeezed me out of that with RTO mandates for architects and above.