Are Overemployed 'Ghost Engineers' Making Six Figures to Do Nothing?

&gt; The Stanford research has not yet been published in any form outside of a few graphs Denisov-Blanch shared on Twitter. It has not been peer reviewed.<p>While I don’t doubt the existence of some useless engineers and people secretly working two engineering positions, the fact that they’re claiming 9.5% of engineers are useless based on the output of some code analysis tool and the paper isn’t even published yet makes me think this is junk science. Is their tool going to mark the engineer with decades of institutional knowledge who mainly spends their time helping others as useless? Or the tech lead who is a manager in all but name but doesn’t have time anymore for code?

Someone commented in a prior thread that they spent an incredible amount of time tracking down a bug that was resolved in two characters of hex. Surely, that person would be marked as a lazy engineer who should get fired. This is meaningless.

&gt; When I asked Denisov-Blanch if his algorithm was being used by any companies in Silicon Valley to help inform layoffs, he said: “I can’t specifically comment on whether we were or were not involved in layoffs [at any company] because we’re under strict privacy agreements.”<p>&gt; I have friends, I call them at 11 am on a Wednesday and they’re sleeping, literally. I’m like, ‘Whoa, don’t you work in big tech?’ But nobody checks, and they’ve been doing that for years.”<p>&gt; [he] said that he imagines a future where engineers are judged more like salespeople, who get commission or laid off based on performance.<p>It&#x27;s amazing how much this guy clearly has an axe to grind about his &quot;friends&quot; and is apparently rewarded for tweeting out unsupported conclusions like &quot;might work multiple jobs&quot; to unpublished, un-reviewed research.<p>Do they not do IRB review at Stanford? Why are you allowed to enroll companies in research by touting that they can use your algorithm to lay employees off?<p>*Technically not a layoff if it&#x27;s based on the employee&#x27;s performance metric but this distinction seems not to matter to the author

My offer still stands: I will do nothing for half the price.

&gt; <i>I asked Denisov-Blanch if he thought his algorithm was scooping up people whose work contributions might not be able to be judged by code commits and code analysis alone. He said that he believes the algorithm has controlled for that, and that companies have told him specific workers who should be excluded from analysis because their job responsibilities extend beyond just pushing code.</i><p>It sounds like this measures &quot;code monkey&quot; productivity, right? Which is fine if you&#x27;re only running it against your code monkeys, I guess - but how many of those can you possibly have?

Should be fairly obvious to any competent manager, or team member, who is contributing regardless of lines of code and who is simply doing nothing. Don’t need a fancy analysis tool for that.

If they want to reduce head count, then reduce head count.<p>If they want counter-productive results, then anoint this Magic Algorithm to do the personnel management, and watch the (purportedly) 90% of productive engineers wast a bunch of time trying to game the Magic Algorithm, if they feel it needful.

If the managers are so checked-out that they can&#x27;t even equitably distribute the work their teams have to do, it&#x27;s really hard to see how any software no matter how magic could help. Seems like it would just give them excuses to be even more checked-out.

It’s interesting the study and toolkit is focusing on engineers. What about engineers management?

Has this Stanford academic ever worked on a production system?<p>If the only tool you have is a pen, the whole world looks like publish or perish.

As you get promoted in the big companies you&#x27;re expected to take more of a mentorship role, doing design reviews, leading teams, running and attending meetings, writing documents, working out conflicts between teams, designing features, designing architecture, triaging bugs, reviewing code, etc., etc.<p>The more you rank up the less actual coding you&#x27;re expected to do. At my last job, after getting promoted to senior engineer I was at times going for multiple month periods without writing any actual code.<p>I&#x27;m not saying it&#x27;s good or bad, I&#x27;m just saying there&#x27;s a lot of senior software engineers that don&#x27;t do much actual coding. The tool might have recorded me as doing nothing when I was all day working on non-coding stuff.

oh no the bosses are coming for us all<p>we&#x27;d better look extra hard-working

where do I sign up for this?

Betteridge would be proud