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.

The FactoryBot gem, previously known as FactoryGirl, is ubiquitous in Ruby and Ruby on Rails testing. If you aren’t familiar with it, you might be wondering, what’s the point? Wouldn’t it be simpler to just build objects myself?

Trying to enforce unconventional coding preferences on a team is an uphill battle. When in doubt, default to convention.

Here are some books that have helped me understand programming. This list is a living document that I plan to update as I read.

How do you introduce new ways of working? We want to bring a new idea to our engineering teams, such as a new command-line configuration, testing tool, or design pattern. But engineers can be discerning and stubborn customers. The idea needs to stand on its own. And, you have to sell it.