Press "Enter" to skip to content

Category: Articles

Longer, more in-depth pieces of writing.

2025 in Books: Software, Business, and Magic

Show Table of Contents
Hide Table of Contents

You Should Probably Read These

I universally recommend these books.

Cal Newport, So Good They Can’t Ignore You.

This book convinced me to stop widening my skillset by beginning again, and start doubling down on my strengths. I loved it so much I recommended it to my wife, and she, too, changed

Gene Kim et al., The Phoenix Project.

This book reinvigorated my love for management, which I lost in 2021–2022. I’m still an IC, but I decided to stop refusing management roles. According to some, this is an IT-oriented retelling of the core ideas behind Eliyahu Goldratt’s The Goal. I haven’t read The Goal, but it was mentioned in The Phoenix Project. And like The Goal, The Phoenix Project is fiction. It’s a novel with a protagonist, antagonist, central theme of conflict, satisfying character development, and gripping plot.

Austin Kleon’s trilogy: Steal Like An Artist, Show Your Work, Keep Going.

These books were cute, full of incredibly quotable passages, and fun to read. I didn’t spend enough time on them, though. A lot of the lessons left my brain like water through a sieve. Since they are so short and enjoyable, I’ll probably re-read them every year or two.

W. Daniel Hillis, The Pattern on the Stone: The Simple Ideas that Make Computers Work

This book is the ideal of edutainment. I have no formal background in computer science, but the author’s writing was so accessible and well-structured that I had no problem following along. It wasn’t a rigorous textbook designed to teach computer science. It was, however, informative and enjoyable.

Read These If You Develop Information Systems

I recommend these, but only if you’re an IT developer.

I Vibe Coded a WordPress Plugin and Shipped it to Production

I haven’t written PHP for over a decade. I haven’t even touched it since 2017. But in the spirit of legitimate peripheral participation, I asked a couple of LLMs to write a WordPress plugin for this blog. Within 15 minutes, I had a proof of concept from ChatGPT. Next, I got Claude to generate an even better version in one shot. I iterated to add a feature and said, “Hey! It compiles! Ship it!“

It was a fun experiment: a microcosm of failure, puzzle-solving, success, and iterative improvement.

Confessions of a Software Developer: No More Self-Censorship

I haven’t published since April because I’ve been afraid. I also avoided social media, news aggregators, and discussion forums for months. I’m done letting fear stop me. What was I afraid of? In this post I detail every single thing I’ve avoided admitting on this blog.

Ship Software That Does Nothing

You should ship software that does nothing. Absolutely nothing. I’m not being cheeky about this. I have no hidden meaning. The very first thing you should deliver when you start a new web application is absolutely nothing.

Many people will tell you to ship a minimum viable product. Others say to ship a prototype to get feedback. Not me. I think you should ship a blank page to your production servers on day one.

Kerrick’s Wager: on the Future of Manual Programming

It’s been a while since I’ve had a crisis of confidence. But tonight, I read Steve Yegge’s recent post, “Revenge of the Junior Developer.” In it, he lays out a vision of a future—only two years away—in which nobody writes code anymore. I felt a cocktail of anger, fear, worry, and disbelief. Then, I thought through the implications, and came up with a plan of action: Kerrick’s Wager.

What Books Should I Read to Learn ASP.NET Core and Blazor?

I’ve been paid to write web applications for over a decade, but my only exposure to ASP.NET has been as an API consumer on the front-end, and I’ve never touched Blazor. That’s changing—I’m learning how to be a full-stack developer. There are almost too many books about the .NET platform, so I had to choose a few to focus on. I started by reading the front matter: the title, cover, foreword, preface or introduction, and table of contents of 24 different books. This was enough to compare and choose the books that I’ll read as soon as possible.

But there are two top contenders for the first book, and I need your help deciding!

I also made a list of 3 books that I’ll read once I’m familiar with T-SQL and the Clean Architecture. 3 more books made my “someday” list—I have no specific plans, but I’d like to read them eventually. At the end of this article I’ll reveal exactly which books made the cut, and ask you to help me choose between two books to learn ASP.NET Core. But first, here are my thoughts on each book.

I Started Reading 26 Books About C# and .NET. Here Are the 2 I’ll Actually Finish ASAP.

I’ve been writing code for money for 17 years, but I’ve never used C# or any other .NET language. That’s changing—I’m learning how to be a full-stack developer. There are almost too many books about the platform, so I had to choose a few to focus on. I started by reading the front matter: the title, cover, foreword, preface or introduction, and table of contents of 26 different books. This was enough to compare and choose the 2 books that I’ll read as soon as possible. I also made a list of 7 books that I’ll read once I’m familiar with ASP.NET and Blazor. 6 more books made my “someday” list—I have no specific plans, but I’d like to read them eventually. At the end of this article I’ll reveal exactly which books made the cut. But first, here are my thoughts on each book.

Fizz Buzz, Object-Oriented Edition: Exploring the Open/Closed Principle With Polymorphism and Metaprogramming

Fizz Buzz, the children’s game turned coding interview question, requires little more than basic programming literacy to solve. But it has just enough complexity that it can also be used to illustrate some important tenets of object-oriented design through refactoring.

30,656 Pages of Books About the .NET Ecosystem: C#, Blazor, ASP.NET, & T-SQL

When I learned lean software development, I abandoned year-long planning at work and at home. This year, I broke my rule. I made a New Year’s resolution. I decided to broaden my skills so I could ship a full-stack enterprise web app completely on my own. No back-end developers, no product managers, no UI designers, and no vibe coding. Since I wrote Ruby years ago and Rails is having a Renaissance right now, I wrote down the following and taped it to my bedroom door:

In 2025, Kerrick is a Full-Stack Programmer

Develop & deploy Ruby on Rails apps, covered by automated tests, to real users.