This is not a guide. This is a bet.
I believe we’re entering an era where one engineer with the right tools can accomplish what previously required entire teams. I don’t know if I’m right. But I’m betting my time, my energy, and my career on finding out.
This site documents that journey.
The Bet
Traditional software development scales linearly: more features need more engineers, more complexity needs more specialists. That’s been true for decades.
I think AI tools change the equation. Not because I read it somewhere or because someone at a big company said so—but because I’m experiencing it. I’m building things I couldn’t have built alone two years ago.
Is this sustainable? Does it scale? Will it work for everyone? I don’t know. That’s what I’m here to find out.
What This Site Is
I’m not here to tell you “the answers.” I don’t have them.
What I have:
- What I’m working on — experiments, tools, ideas in progress
- What I did — finished projects, with all the wrong turns included
- What I learned — not universal truths, just my takeaways
- What worked for me — maybe it works for you, maybe it doesn’t
I show the work raw. The successes and the failures. Movement is life. Movement is learning. Movement is evolving.
The Methodology: Pólya’s Four Steps
So how do I approach all this experimentation? I try to follow George Pólya’s framework from “How to Solve It”:
- Understand the problem — What am I actually trying to solve?
- Devise a plan — What’s the smallest thing I can try?
- Carry out the plan — Build it, ship it, use it
- Look back — What worked? What didn’t? What do I carry forward?
Step four is the important one. Every experiment—success or failure—produces learning. That learning compounds. That’s how one engineer builds leverage.
On Credentials and Curiosity
I don’t work at OpenAI. I don’t work at a big tech company. I’m an engineer in a different trench, seeing different things.
I believe curious, dedicated people can have valid perspectives regardless of where they work. Different experiences create different insights. Some will be valuable, some won’t. That’s fine. The point is to share them, test them, and learn.
You might disagree with my approach. Good. Tell me why. Maybe you’re right. Maybe we’re both right for different contexts. Maybe my brain just works differently than yours.
All of that is part of the process.
The Invitation
This isn’t “One Engineer Who Has Infinite Leverage.” It’s “One Engineer Pursuing Infinite Leverage.”
I’m walking towards something I believe is possible. I could be wrong. I’m sharing the journey so you can:
- Watch and learn (from my wins and my mistakes)
- Disagree and push back
- Try your own experiments
- Share what you find
Movement is life. Let’s move.