Just take the next step

Except in the most extreme situations, you’ll find how to build something a lot easier than knowing what would be worth building.

Example, a time machine would obviously be pretty handy. You could go back in time and not sell that bitcoin you doubled from roughly $100 to $200–totally hypothetical example, of course. But good luck knowing how to build it.

But software developers and people who employ software developers know how to build things, and so that’s what they do.

What if instead you lean into the hard parts? Do the hard parts first. Talk to your customers. Understand their problems, and hypothesize solutions to those problems. Make simple prototypes and show them to your customers. Just take that next step into the dark.

I’ve heard this process described as wasteful before, which genuinely blows my mind 🤯. It gets you customer feedback pretty quickly.

The only alternative I’ve seen is building entire products before getting that first piece feedback. If you really nailed to product on your first attempt, for sure that would be cheaper. But the odds of it are like hitting a bullseye in one shot.

Oh, and the dartboard is sitting on Pluto. #StillAPlanet #NeverForget


Like this message? I send out a short email each day to help software development leaders build organizations the deliver value. Join us!


Get the book!

Ready to learn how to build an autonomous, event-sourced microservices-based system? Practical Microservices is the hands-on guidance you've been looking for.

Roll up your sleeves and get ready to build Video Tutorials, the next-gen web-based learning platform. You'll build it as a collection of loosely-coupled autonomous services, developing a message store interface along the way.

When you're done, you'll be ready to contribute to microservices-based projects.

In ebook or in print.