Build before you are ready

Before I worked in technology sales, I was buying broken phones and teaching myself how they worked. I liked figuring out what was wrong and seeing whether I could fix it. Learning to build software has brought me back to that same curiosity.

I didn’t study software engineering. I started with problems I wanted to solve and learned what I needed as I went. That’s still how I approach the work.

Start with something you understand.

Kouri grew out of my own experience as a runner. I learned there was a difference between putting in miles and understanding how to train. I wanted coaching that helped connect the plan, the run, and what I should do next.

The first time I completed a real run with software I’d built working on my iPhone, something clicked. I’d taken an idea far enough to use it in my own life. There was still plenty to improve, but I could see what I was building toward.

Trying it teaches you what’s missing.

I can think through an idea for a long time and still miss something that becomes obvious the moment I use it. Building a first version gives me something specific to learn from. Then I have to do the less exciting work of testing, fixing, and improving it.

AI has helped me learn and build faster. I still need to understand what I’m making, check that it works, and take responsibility for it. That part stays with me.

If you’ve been sitting on an idea, try making one small part of it work. You don’t need to give yourself a new title first. You can start learning by doing.

Explore the talk: The Person Is the Asset