Writing
Notes on building.
Short, practical pieces on systems, AI, and calm infrastructure.
This is where I think out loud about the craft of building software that pays off — web performance and conversion, AI automation done properly, e-commerce decisions, and the DevOps that keeps everything calm. No hot takes or hype cycles; just the practical lessons I've picked up shipping real projects for real businesses. If you're a founder or operator trying to make a smart call about your website, store, or automation, start here.
Build systems that compound, not tasks that repeat
A practical way to choose a first automation: map the workflow, calculate its full operating cost and plan for exceptions.
Read June 5, 2026AI agents that actually book leads
Define an agent's job, connect approved information and booking tools, and evaluate handoff before it handles customer enquiries.
Read May 18, 2026DevOps without the 3 a.m. call
Make releases recoverable with a documented deployment path, useful checks, clear ownership and a rehearsed rollback.
Read April 28, 2026Why fast websites make more money
Review website performance alongside content and enquiry journeys, and distinguish lab scores from customer outcomes.
Read April 10, 2026Shopify or custom: which does your store actually need?
Compare Shopify and a custom storefront through catalogue, checkout, integration and ownership requirements before choosing a platform.
ReadExplore and plan
Notes for people building and operating useful software.
This collection brings together the reasoning behind the work: how software is structured, where automation helps, and what makes a product easier to maintain. Start with the article that matches the decision in front of you.
Read with a concrete question
You might be deciding whether to automate a workflow, improve a website or change a deployment process. Keep that question in view as you read. A useful article should help you identify tradeoffs and the information you still need before choosing an approach.
Connect an idea to a practical example
Move from an article to the relevant case study to see implementation context. Use the free calculators to explore a budget or workload with your own inputs. Their outputs are estimates, so replace sample assumptions with information from your business.
Put the advice in context
Tools, vendor terms and operating conditions can change. Check the article's date and verify external details before making a purchase or changing a production system. The underlying decision process can remain useful even when an implementation needs updating.
Questions about Software Engineering, AI Automation & DevOps Writing
Where should I start?
Choose a post related to your current problem. For an overview of my approach, read the Thesis page.
Can I discuss an article in relation to my project?
Yes. Include the article link and explain your own requirements through the contact page.