Thoughts on being a programmer

<i>Be yourself. </i>Code for fun. <i>There's hundreds of ways to write the same thing, don't be a dick about your way, but stand up for good practices. </i>Respect those who accomplish great things, because it was a lot of work, even if they say it was a weekend practice, they took a lot of time to get to that point. <i>If you code correctly, one line changes are possible. </i>Learn to desire success more than you fear failure. (I like this one) <i>Don't become the old people you hate, always try to learn new things, no matter how alien. </i>Who cares if you're coding on production live? Right? Right? <i>Comments are for the weak, tracing and prototyping code is not. </i>Mistakes are inevitable *It's hard being the smartest person in the room sometimes, wear it with humility rather than pride.<p>My version of the list. This was fun!

Something in one of Zed Shaw's old talks stuck with me. Roughly:<p><i>"Don't go with the flow of the industry. Try [unconventional] things because there's something beneath [software] that we haven't figured out yet."</i><p>I suppose there's two personal disclaimers:<p>- I'm not that interested in the business aspect of software.<p>- The answer to what the magic beneath is may elude me due to it simply being "math, stupid".

I liked "err vicariously" ;-)<p>It's good to learn from your own mistakes, and even better to learn from someone else's.

&#62;Always back up before tidying up. I liked this piece of advice, it's a lesson we all hate to learn.

I would add: Don't release on a Friday.

Communicate often. Have a beer with a fellow programmer. Don't be afraid to break code.

&#62; There's always plenty of room for improvement - in your code, in your abilities, in you.<p>I just saw an amazing movie about a man that embodies this philosophy: "Jiro Dreams of Sushi"[1]. This man's dedication to further mastering his craft is unparalleled. Even though he is widely regarded as the best Sushi chef in the world, he is still singularly focused on becoming better every day.<p>I highly recommend watching - it's very inspiring.<p>[1] <a href="http://en.wikipedia.org/wiki/Jiro_Dreams_of_Sushi" rel="nofollow">http://en.wikipedia.org/wiki/Jiro_Dreams_of_Sushi</a>

Work on unimportant problems. <a href="http://www.yosefk.com/blog/work-on-unimportant-problems.html" rel="nofollow">http://www.yosefk.com/blog/work-on-unimportant-problems.html</a>

The bit about there always being room for growth was driven home for me yesterday as I was looking through how to build an object model in PostgreSQL using object-relational features. I went through the features one by one and discovered that I had only scratched the surface of that aspect of PostgreSQL. I suddenly understood how to rethink what I was doing in terms of design patterns in order to build object interfaces in the db for the relational underpinnings.

It is written so beautifully that the "code" part of these thoughts can be substituted for many other things: design, engineering, life etc.

<i>Don't be an asshole</i><p>Agreed but on the page, it looks a bit of out of place with the other points.<p>My mind fills in the details as "don't act like you are the programmer who's a hundred times more productive than the others, even if it seems like you are".<p>But that's a big question. Apple Computer arguably expects its programmers to all be the x100 producers and was managed by someone who it more or less was admitted to be an asshole (a genius, inspiration, unique asshole but still an asshole).<p>So it think the greatness and asshole-dom question is not settled for people even if I would embrace it.

"Err vicariously"<p>Loved that. Subtle, yet deep!

That was a short, concise, pragmatic, wise and rockin article.