What to build next
AI can build anything, but what's really worth building?
A lot of developers are now asking:
What skills should I develop? Which framework, which language, which area do I go deep on?
I have an opinion on the language: learn Rust, but for the rest it's a moving target, and the list of skills we need seems endless.
I would flip the question though: instead of what to learn? I would ask: what's worth building?
Answer that, and the skills, areas, and expertise you need will fall into place.
That's where I'd start. Not learning another framework for the sake of it, but letting what to build dictate what to learn. AI hasn't changed this. It's what gave me a headstart in software years ago.
So the question becomes:
What's the most valuable thing you're waiting for permission to build?
Already have an idea? Scope it into a one-page MVP brief in ≈30 min, based on the Scope First technique I developed (articles). It will help you clarify your idea, and give you a clear direction to start building.
Not sure yet what's worth building? That's fine too. Brainstorm it with me first.
How I've used this technique to go from idea to MVP
Ask the Canon
One idea, scoped first. From downloading Gutenberg book texts to building a semantic search without vector db.
checkpulse
Privacy-first analytics in a single binary. Scoped to MVP, built in Rust, deployed on Fly.io.
Pybites Platform
A full Python learning platform, in production for years. The MVP was tightly scoped around exercise solving.
mdweaver
Turn one or many Markdown files into polished PDFs and EPUBs. A small tool with a focused scope: do one job well.