2 ms·
Philip Greenspun in Founders At Work (p. 325): The people who were really good software engineers were usually great writers; they had tremendous ability to or
by gruseom 19y ago
Philip Greenspun in Founders At Work (p. 325):
The people who were really good software engineers were usually great writers; they had tremendous ability to organize their thoughts and communicate. The people who were sort of average-quality programmers and had trouble thinking about the larger picture were the ones who couldn't write.
I posted this before (http://news.ycombinator.com/item?id=127743 http://news.ycombinator.com/item?id=127743), but that thread was already old, and it's relevant here too.
Edit: I'm not sure I agree with the (slickedit) post, though. Saying "Learn to write" is more like saying "Learn to think" than "Learn to drive". One can improve and refine, but by the time a person gets to be a professional programmer I don't think one is likely to see order-of-magnitude improvement.
- hernan7 19y agoReading good prose helps. Also, rewriting.
- gruseom 19y agoBut good writers are far more likely to do these things than bad writers are. Among what Greenspun calls the "average-quality programmers", I can't think of many who could care less about reading good prose (they read MSDN at best), or about rewriting anything at all (even their code).