After a decade of programming full-time, I’ve developed a daily work routine that I’d like to share. I hope to revisit it and share it with people who are starting out in the industry or are curious about a programmer’s workday.

There are only two hard things in Computer Science: cache invalidation and naming things. – Phil Karlton

Let’s talk about variable name antipatterns!

Code coverage, the percentage of your code covered by automated tests, is a metric associated with quality. In this post, I’d like to investigate this association. And pour some cold water on it.

Here’s an argument that’s gaining momentum in my field: AI will eliminate or greatly reduce the programming profession.

Here are some one-sentence summaries of books that have helped me understand programming and technology.

Retrospectives are one of my favorite engineering team practices. In this post, I’ll explain why and how I run retros.

There’s been a lot of recent discussion in the TypeScript community about typing functions. These arguments tend to take binary positions: always type your functions, or never type them unless the compiler demands it. Which is the best option?

CRUD is an acronym that’s used a lot in web and mobile development. Frontend engineers in particular might wonder what it means and why we use it. In this post, I’ll explain CRUD using PostgreSQL, and talk about why it’s important.

Have you ever wanted to create a timer in a React app? This could be in support of a UI timer or polling. In this post, I’ll explain how to create a timer effect in a React application using hooks and setInterval.

When I am preparing development work, I write Gherkin-style stories, which follow the “Given/When/Then” format. I learned this technique at Hashrocket and have practiced it ever since. It’s incredibly effective. But why? In this post, I’ll try to answer that question.