> The better you write, the higher you go in Ogilvy & Mather. People who think well, write well.
Most of this advice applies to coding as well (with some liberties...):
1. Read Effective Java / Effective Go, etc
2. Use normal idioms of the language, not clever constructions.
3. Short variable names, short methods, short classes.
4. Don't force "Patterns" into your code unnaturally.
5. 1000 lines to a file, max.
6. Check the APIs you use (at least the docs), that they do what you want them do.
7. Don't submit code the day you write it in a fury of creation. Sleep on it and review it the next day, and clean it up.
8. Code Review.
9. Write clear understandable code, not just code that you fiddled until it compiled and ran.
10. Don't just send an email and expect the reader to act. Talk to the person to get their commitment.
> The better you write, the higher you go in Ogilvy & Mather. People who think well, write well.
Most of this advice applies to coding as well (with some liberties...):
1. Read Effective Java / Effective Go, etc
2. Use normal idioms of the language, not clever constructions.
3. Short variable names, short methods, short classes.
4. Don't force "Patterns" into your code unnaturally.
5. 1000 lines to a file, max.
6. Check the APIs you use (at least the docs), that they do what you want them do.
7. Don't submit code the day you write it in a fury of creation. Sleep on it and review it the next day, and clean it up.
8. Code Review.
9. Write clear understandable code, not just code that you fiddled until it compiled and ran.
10. Don't just send an email and expect the reader to act. Talk to the person to get their commitment.