Insights
I write about the lessons I've picked up building software products, scaling systems, leading engineering teams, and solving real technical problems for the businesses I work with.
10
Articles Published
8
Topic Categories
7 min
Avg. Read Time
Browse by Topic
A WooCommerce store can grow quickly while technical problems quietly increase costs. Here's how performance, tracking, plugins, hosting, security, and architecture affect ecommerce growth.
Not every manual task is worth automating with AI, and not every AI automation project pays for itself. Here's how to tell the difference before you build one.
Most growing companies don't actually need a full-time CTO yet. Here's how to tell what you actually need before you make an expensive hire.
A practical framework for deciding whether your software needs a full rebuild or a targeted refactor, before you spend the budget on the wrong one.
Every outage teaches the same handful of lessons in a different costume. Here are the ones that actually changed how I build.
Each path solves a different problem. Picking the wrong one for your stage is one of the most expensive mistakes founders make.
A discovery call isn't a sales pitch — it's the first fifteen minutes of the engineering process. Here's the exact structure I use.
Not every architecture decision needs to be right on day one. These four do — because they're expensive to reverse once you have paying customers.
Technical debt is usually discussed in the abstract. Here's how to actually quantify it, and when paying it down is the cheaper option.
Common Questions
No fixed schedule. I write when I have something genuinely useful to say, not to hit a quota.