
A noted blogger and author of Joel on Software explains how companies can find and hire the best programmers available, offers practical suggestions and tips on how to identify great developers, sort resumes, interview candidates effectively, and more. (All Users)
Still a great read. Base idea is that they're smart enough to solve problems and they get things done and don't just blab about ideas which they won't implement. So they'd write code to prove they can get things done.
Brainteasers were okay, but bad at testing the latter. This somehow evolved into Leetcode culture or take home assignments.
https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guid...
For example, his book Smart and Gets Things Done[1] is great.
Although not management, per se, Steve McConnell's stuff[2] has been of invaluable assistance, in my career. He talks about Quality Process, and that's the kind of stuff that managers should (IMO) know and enforce. Again, I don't think folks, hereabouts, have much love for him.
His book, Rapid Development[3], was a watershed, in my development.
[0] https://www.joelonsoftware.com
[1] https://www.joelonsoftware.com/2007/06/05/smart-and-gets-thi...
[2] https://stevemcconnell.com
[3] https://www.microsoftpressstore.com/store/rapid-development-...
Check it here: http://steve-yegge.blogspot.com/2008/06/done-and-gets-things...
[0] https://www.joelonsoftware.com
[1] https://www.joelonsoftware.com/2007/06/05/smart-and-gets-thi...
When swe work conditions discussion reaches this point I always remember Spolsky's brilliant "Smart and Gets Things Done" book. He writes about KPIs a bit, just enough to not treating it too seriously.
