I do a lot of code reviews, and it’s very obvious who on the team barely churns out useful code —- even just from the low density and volume of their code.
The primary role of leadership is to feed tasks and guidance to skilled people who your organization has selected based on known temperament and skillset.
If you run a software company and don't know you employ who can code you are at titanic slipping beneath the waves status still calling on skilled ship designers.
It's done he burned 44B by being a bad leader.
Most engineers should be able to run “git log -p —author=myname —since=‘12 months ago’” and find 10 examples of non-trivial code.
And those that can’t, should be able to provide a good explanation of what they contribute instead.
I’m guessing the screenshots themselves will be less relevant than their owners’ description of what the depicted code actually does.
This is all very dumb and I’m not defending the way he’s doing this.