>> 9. Read other people’s code > I have NEVER liked this advice. The only way I'm able to read code is when I'm actively working towards some goal. Usually th

>> 9. Read other people’s code > I have NEVER liked this advice. The only way I'm able to read code is when I'm actively working towards some goal. Usually this is extending or fixing the existing code in some way. Sometimes it's to extract a specific algorithm or technique for some project of my own. That can certainly be enlightening, whereas just plain reading the code sends me to sleep. Basically, that turns the advice into: - either participate in an open source project (bugfixing, implementing features) - or integrate/convert some complex piece of open source code into/for a project of your own I definitely think there's something to be gained (learned) from read/write hacking rather than (mostly) write-only. Obviously, if you're trying to get stuff done, all that goes out the window, just get the damn thing written, by whatever means it takes.