Free learning track
Choosing a stack you will not regret
Four questions that decide the answer, and why the most interesting option is frequently the wrong one.
Who this is for: Anyone deciding what to build something in, especially for a client.
What you will be able to do
- Ask who maintains this in two years, first
- Match rendering strategy to how often content changes
- Treat existing constraints as inputs rather than obstacles
- Recommend against your own preference when the constraint says so
The material
Articles in this track
Written and published. No sign-up, no email gate.
Why my portfolio runs on six different stacks
Static HTML, WordPress, hand-written PHP, Astro, a Vite SPA and Next.js — one portfolio, all correct. The stack follows the constraint, not the preference.
Read itTell me what you're building.
Two minutes on the brief form gets you a real conversation: what the software has to do, what it will take, and an honest read on feasibility — whether or not we end up working together.