Project 02 has a code name
What I can say about it so far, and the calls I made along the way.
Project 02 has been on my laptop since September 28. I’m not ready to tell you what it is yet. Partly because it isn’t live, partly because a little mystery is more fun. So for now, it gets a code name: Ember.
Here’s where it’s at, and a few calls I made along the way.
Where it’s at
It fully works on my laptop.
But working on my laptop isn’t the same as ready for you. Before launch, I still need to:
- Test it more.
- Run a security scan.
- Build the whole infrastructure: hosting, domain, database, emails.
The calls I made
I went simpler. The first version in my head had accounts, an inbox and weekly AI research. I spent a full day on the landing page alone, and it got busier with every version. But the idea was pretty niche, and not that exciting. So I pivoted to something simpler. It won’t bring in any MRR, but it’s cool and simple to use.
AI for some parts, rules for others. Not everything needs AI. Some parts it does really well, like writing and suggesting. Other parts are better deterministic: same input, same answer, every time. So I split it that way.
Real data humbled me. Almost every rule I wrote looked perfect on paper and was wrong the first time I ran it on real projects. 15 years in, and the data still gets the last word. I fixed the rules, not the data.
Correct isn’t enough. The first working version was fair, accurate… and boring. I looked at it and thought: nobody is going to share this. So I kept the engine, changed the attitude, and gave it a new name. You’ll see it soon.
What’s next
Tests, security, infrastructure, then launch. The real name comes with it.
If you want to be there when it drops, pull up a chair.