The right way to ask a question to get an answer

Dear new developer, I already covered the right way to ask questions, but this post was so good that I wanted to share it. (I found it on hackernews.) Mike Ash gives advice on how to get answers from the internet. Tips like "explain everything up front", "post your code" and "follow up after you … Continue reading The right way to ask a question to get an answer

Letters to a new developer from Joel Spolsky

Dear new developer, Looks like Joel Spolsky has written a number of blogs posts aimed at new developers. Every post is tagged with the date so you can be aware of any old posts that may have dated advice. But I've been following Joel since a colleague emailed the Joel Test around our workplace in … Continue reading Letters to a new developer from Joel Spolsky

Justin Kan on whether you should work at a startup

Dear new developer, Justin Kan has deep experience in the startup space, including at an accelerator called Y Combinator. He gave a talk about why you should work for a startup, and why you shouldn't. Here's the transcript,, and here's a blog post based on it. If you're looking for good management, avoid startups: The … Continue reading Justin Kan on whether you should work at a startup

How to market yourself as a new software developer

Dear new developer, This post from Corey Snipes, an experienced software developer, is well worth a read. From the post: People skills help so much. It’s hard to overstate that. I am a competent software developer, but I am really good at working on a team and that has carried me to increasingly sophisticated and … Continue reading How to market yourself as a new software developer

Laziness, impatience, hubris

Dear new developer, Larry Wall has created foundational software (perl, patch). He coined the three virtues of a programmer: Laziness: The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don't have … Continue reading Laziness, impatience, hubris

Understand the business

Dear new developer, Your code is written to further some end. It could be for academia, government, or, more likely, for business purposes. In all the cases, having a greater understanding of these overarching purposes will allow you to make smarter decisions and write better systems. However, just like in software development, business uses a … Continue reading Understand the business