-
Why the SaaSpocalypse is over blown
Predictions state AI will replace SaaS platforms with custom software. This resembles the open source movement. Building custom tools creates costs for security, maintenance, and integration. Established providers offer compliance and scalability. Focus on your core business. Use AI to enhance your tools instead of replacing them. Always stay practical.
-
Unlocking Cursor: Features and Workflow Tips
Want to get a little more out of Cursor, the AI development environment? I walk through the major components with hints and tips on how to get the most out of vibe engineering with rules and agent modes.
-
Future of AI is not public
If all you can do is to refresh the Status Page, then you are not in control. Relying on public AI SaaS providers is not a long term future play. You have to take control if AI is integrated to everything you do.
-
[Review] PostgreSQL Mistakes and How to Avoid Them
If you are running PostgreSQL in production at any sort of scale, then you need this book on your shelf, as it will lift the lid on some of the things that will make your database sing.
![[Review] PostgreSQL Mistakes and How to Avoid Them](https://alan.is/wp-content/uploads/2026/02/mycousinvinny-small.png?w=643)
-
Five Nights of Vibe Coding: A Game Experiment
I built a game with Claude using vibe coding. The game works and is fun, but I feel no pride of ownership. Is the game my creation, Claude’s, or the millions of developers to which Opus learned to code from? The whole experience has left me feeling rather flat.
-
“Well pick it back up”
Monitoring systems for failure is more art than science, with many systems firing off way too many false positives. Getting your arms around this is not easy, but we all need our “fall detection necklace”
-
Vibe-factoring Java with Claude
Writing and refactoring code with Claude AI agents, on the whole was a fantastic usage of AI in software development. Was not completely without hurdles but the code was better for it.
-
Planning for the inevitable end
Software maturity requires planning for the inevitable death of your users. You must implement marketing kill switches, clear data retention policies, and account delegation. Stop annoying grieving families by automating bereavement reporting and protecting user namespaces. Building these mechanisms proves your organization handles every user stage with the respect deserved.
-
The Shiny Object Trap: Don’t forego the basics
Software quality declines as leaders chase shiny features while ignoring basic reliability. Outlook fails at calendar imports. PowerPoint uses ancient tools. This complexity creates security risks. You must audit your core tasks and fix friction first. Do not add new code until the fundamentals work every time. Reliability is everything.
-
Reclaiming Focus: The Lost Art of Downtime
Modern software builds traded the forced tea time of Borland Turbo C for complex YAML pipelines and noisy distributed failures. To avoid burnout and logic errors, you must reclaim your time to think. Build a fake commute, step away from the screen, and go make a proper cup of tea.
the leg-end that is, Alan Williamson.
For over 20 years, I’ve shared my thoughts whenever the muse strikes. It’s unpredictable, honest, unedited, and occasionally witty. I’m living the best years of my life, working harder than ever, and enjoying every second.
Alan Williamson 