Building for Ease of Change
The most important quality in a digital tool right now isn't what it does today — it's how easily it can be updated tomorrow.
← CreatingOptimize for changeability—not feature completeness, performance or elegance.
The ability to update quickly and cheaply without breaking other things is the top prioity because of the increasing pace of change in tooling and AI capabilities.
The rate of capability available to builders is faster than most product cycles are designed for. If you build something that’s hard to change, you’ve built something that will be outdated, insecure and expensive to fix.
For this site, it meant choosing Astro and a file-based CMS. No database to manage, no complex deployment pipeline. Content lives in Markdown files. Styles live in one place. The structure is explicit and shallow.
When I want to change something — add a section, update the design, add a new type of content — I can do it without breaking or touching things that should stay the same.
The tradeoff requires more thought upfront to resist the temptation to use services that offer more than what’s needed for the purpose, hard to alter and offboard without fear.