The Competent Developer
Nov 28, 2018
The canonical and extended version of this post now lives here:
A developer should be able to improve legacy, plan an architecture, write a ticket, run a release, understand users, give feedback, receive feedback, optimise, hack it, build infrastructure, abstract away detail, pair, act alone, challenge requirements, chair a meeting, pitch the product value, document, hire, refactor, release, rollback. Specialisation is for insects.
Inspired by Robert Heinlein’s competent man
