I've seen occasional articles about how to manage programmers. Really there should be two articles: one about what to do if you are yourself a programmer, and one about what to do if you're not. And the second could probably be condensed into two words: give up.
About this quote
- What does it mean?
- Managing programmers requires different approaches for programmers versus non-programmers, with the latter often needing to step back.
- In plain terms
- If you are not a programmer, you should probably stop trying to manage them closely.
- What can you take from it?
- Non-programmers lack the context to manage coding work effectively.
Where it applies
Putting it to work
Questions to consider
- Who should manage technical teams?
- What skills does management require?
Another view
Some non-technical oversight is still necessary for business goals.
More from Paul Graham
When those far removed from the creation of wealth -- undergraduates, reporters, politicians -- hear that the richest 5% of the people have half the total weal…
Permalink to quote #11 At any given time, there are only about ten or twenty places where hackers most want to work, and if you aren't one of them, you won't just have fewer great ha…
Permalink to quote #13 A programming language is for thinking of programs, not for expressing programs you've already thought of.
Permalink to quote #10
Related quotes
You manage things, you lead people.
Grace HopperGrace Hopper quote #13 Beware of Methodologies. They are a great way to bring everyone up to a dismal, but passable, level of performance, but at the same time, they are aggravating …
Joel SpolskyJoel Spolsky quote #3 I can be President of the United States, or I can control Alice. I cannot possibly do both.
Theodore RooseveltTheodore Roosevelt quote #9