In "Holding a Program in Your Head", Paul Graham, co-founder of Viaweb and writer of "Beating the Averages", argues that "your code is your understanding of the problem you're exploring. So it's only when you have your code in your head that you really understand the problem."
Here's his list:
- Avoid distractions
- Work in long stretches
- Use succinct languages
- Keep rewriting your program
- Write re-readable code
- Work in small groups
- Don't have multiple people editing the same piece of code
- Start small
Read about it at: infoq
No comments:
Post a Comment