Chapter 10—What You Build Next
You now have a methodology for building real software with natural language coding. Not demos. Not toys. Software that works, handles failure gracefully, and can serve real users. But the Jetty Method isn't the destination. It's a starting point.
Making The Jetty Method Your Own
The principles here, specification before implementation, incremental hardening, structured workflows, isolated experimentation, these aren't tied to any particular tool. They're patterns that work. I encourage you to take these ideas and make them your own. Build workflows that fit how you think. Design tools that encode the practices that matter to you. The best system is the one you'll actually use.
I'm building a tool called JettyPod that implements the Jetty Method directly. It handles the worktrees, tracks the work items, guides you through the modes, and keeps your AI assistant on the rails. It will be available soon. If that interests you, I’d encourage you to join the waitlist.
Whether you use JettyPod or build your own system or simply carry these ideas in your head as you work, you're now equipped to build software that lasts.
We're at the beginning of something significant. The ability to translate ideas directly into working software, without years of technical training, without venture funding, without engineering teams. This changes what's possible. Problems that were never worth solving because the cost was too high are suddenly within reach. People who deeply understand those problems can now build the solutions themselves.
You're one of those people. You picked up this book because you have something worth building. Now you have a way to build it.
I'd love to hear what you create. Questions, comments, success stories, hard-won lessons, send them my way. You can reach me at espangenberg@gmail.com. I read every message.
Go build something great.