Writing Is An Undervalued Engineering Skill

Dear new developer, This post discusses writing and how learning to write well can really level up your engineering experience. You can also view over 300 comments about this post on one of my favorite online communities, Hacker News. The author has some suggestions on how to become better: So how can you work on … Continue reading Writing Is An Undervalued Engineering Skill →

Programming Is Terrible, So Learn To Enjoy It

Dear new developer, I appreciated this post which talks to people who are interested in being a developer, rather than someone who is newly a developer. I still think a lot of things apply. This especially resonated: ...programming is terrible, so learn to enjoy it. If you are “on the net” learning about what programming … Continue reading Programming Is Terrible, So Learn To Enjoy It →

Beware Of Your Arrogance

Dear new developer, I wrote this post years ago, but it still applies today. Ah, the arrogance of software developers. (I’m a software developer myself, so I figure I have carte blanche to take aim at the foibles of my profession.) Why, just the other day, I reviewed a legal document, and pointed out several … Continue reading Beware Of Your Arrogance →

Egoless programming

Dear new developer, This post is worth reading in full, but is advice that holds for all developers, not just folks starting out. I especially liked Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don't take revenge … Continue reading Egoless programming →

Avoid being an expert beginner

Dear new developer, This post by Erik Dietrich covers the situation where a developer becomes an "expert beginner". This is something to avoid as you build your career--don't work in a place where you are isolated or unable to progress. He breaks progress in any area down into a number of components--Beginner, Advanced Beginner, Competent, … Continue reading Avoid being an expert beginner →

How to read code

Dear new developer, Reading code is much more common than writing code. Some might even say, "don't trust any documentation, read the code," though I consider that to be a pretty radical position. But how can you effectively read the code. This post from selftaughtcoders.com gives a good explanation: Find one thing you know the … Continue reading How to read code →

Start at a small consulting company

Dear new developer, If you are sure where you want to go in your shiny new development career, pick that and follow it. Whether that is embedded programming or high frequency trading or generic web development, pursuing a career with focus is a great option. If you are just looking for that first job, remember … Continue reading Start at a small consulting company →

Think deeply about engineering management

Dear new developer, This post from Charity about the choices you face as an engineer, and the challenges of technical management, is wonderful. As a new developer, you're probably a few years away from thinking about that (but perhaps not. If you join a startup rocketship, it's possible you'll be managing people in months). But … Continue reading Think deeply about engineering management →

Opportunity Cost and the Internet

Dear new developer, Seth Godin writes every single day on a variety of interesting topics. He's been blogging for years and years. Definitely an interesting person to follow. I saw this post on opportunity cost in my RSS reader (you should use one) and thought it was an interesting take on all the free content … Continue reading Opportunity Cost and the Internet →

What Mitchell learned in his first two years as a software developer

Dear new developer, It's great to see what other developers have learned, especially when they are just starting out. This is a post covering Mitchell Irvin's lessons from his first two years as a software developer. Now, I don't know Mitchell at all (but I guess I am connected to him in the third degree, … Continue reading What Mitchell learned in his first two years as a software developer →