Posts

Great developers review their own code often and effectively. In this post, I’ll share a checklist of all my best tips for maximizing this important practice. ...

I’ve been lucky to have worked with some great engineers, and one thing that they tend to do exceptionally well is reporting about their work at meetings. Today I’d like to summarize what I think makes a great standup report. ...

As a mentor at Code Platoon, I’ve been able to help many people transition into programming. In this post, I’d like to focus on a vital part of that process: crafting your transitioning-to-tech resume. ...

Today I completed the ‘Resistor Color Trio’ TypeScript exercise on Exercism. Here’s my solution. ...

Today, I’d like to dive deeper into a part of my practice: using a persisted text file for jotting things down. In this post, I’ll explain the ‘why’ behind this technique, and provide an updated version of it. ...

Some advice I offer people entering the programming profession is to buy the best hardware you can. You’re going to need it. ...

Today as a code kata I completed the ‘Resistor Color Duo’ TypeScript exercise on Exercism. Here’s my work. ...

The exit code of a command in a Unix-based system is an important and easy-to-miss piece of data. It isn’t printed to standard out; you have to go looking for it. I find it useful to inspect this information when debugging or considering chaining unfamiliar commands. ...

I saw a meme this week: a person debugging code, “My code doesn’t work. Let’s change nothing and run it again.” This is something that I’ve done. It seems pointless. But that’s not quite correct. ...

When learning a new language or framework, the first thing I do is read the official documentation cover-to-cover. ...