Published: October 13, 2021 • 2 min read
What should you focus on at the beginning of your career?
My answer is: being really good at programming.
I wish I’d heard this advice earlier. It would have saved me some cycles.
☝️ Caveat: this assumes that you have basic people skills. The programmers that I meet through Code Platoon are all veterans or military spouses, typically older than the average entry-level programmer, and among that cohort this assumption has been uniformly (pun) true. People skills are the price of admission to any successful career. They matter as a programmer even more as you advance. Don’t neglect them.
There’s a quote from Steve Martin, and a book by Cal Newport named after it: “Be so good they can’t ignore you.” Programming is tough. There is an insane amount to learn across languages, platforms, and tools. You’re going to be building and outgrowing mental models, breaking through limitations, forcing yourself to consider ideas that are counter-intuitive to you. Just when you think you’ve got it all figured out, it changes. Sit next to us at the fire hydrant and have a long drink.
Don’t worry about taking the right job at the right company. When you’re starting out those opportunities aren’t going to be busting down your door; forget them for now. Don’t worry about learning the right language or framework. Once you can program, you can pivot. You have to be a good programmer first to even have that problem.
To quote Cheryl Strayed, author of Wild: “Don’t be in a hurry to publish. Be in a hurry to be the best writer you can be.”
“Don’t ask for advice, ask for a code review.”
A signpost that somebody has adopted this attitude and is headed in the right direction can be gleaned from how they respond to pairing or a code review. When a great programmer critiques your code, they’re trying to do just two things: improve the code and you as a programmer. That’s it.
But there’s a big conflict! When you’re new, your code is going to be bad. You’re going to implement anti-patterns. Take pointless risks. Step right on invisible third rails. Ignore obvious cases. Anyone who has ever opened a text editor has made these mistakes.
Folks who are headed in the right direction engage with the ideas. They try to figure out what they missed by asking questions. Folks who are stuck on the plateau of beginner-ism will “well, actually” themselves right past the message, arguing, appealing to authorities, and throwing up every logical fallacy in the book because it is painful to feel like somebody is criticizing your mind. They aren’t, but it can take a while to figure that out.
If you want to grow, have agency, and be passionate about your programming career, get good at it. Everything after that will be easier.
✉️ Get better at programming by learning with me. Subscribe to Jake Worth's Newsletter for bi-weekly ideas, creations, and curated resources from across the world of programming. Join me today!
Blog of Jake Worth, software engineer in Maine.