Building in public before I launch.
Not for vibes. So when the product ships, there's already people who care.
What you'll get here:
- honest founder notes
- AI/build takes that aren't fluff
- the messy middle, not the highlight reel
If that's useful, follow along.
my new AI native software engineering principle is to delete as many layers of abstraction as possible
at this point, all my webapps are written in rust and compiled to wasm, UI is rendered directly in html and/or raw webgpu calls
no react/threejs/nextjs or any other intermediary abstractions
all my effort goes into writing custom validation harnesses for each app that fully quantifies perf / usability / what "good" means for the coding agent so it can hillclimb it
every agent sessions are planned via my explore unknowns skill (https://t.co/ny5PejnLTK), so all major decisions are frontloaded, then I just let the agent rip for 12+ hrs
at this point I'm solo shipping products that I wouldn't even dare to dream of a year ago
So I was trying to understand why pull requests speeding up the Elixir version were being denied by the clankers while they were being accepted to Go/Express/Rust.
It turns out that, not only each project had a different starting point and a different prompt, but also each project also has a different set of verifications that they are required to pass!
For example, Elixir is the only guided to "preserve the pinned Rails reference behaviour", the only with a explicit verification that we are using Redis and draining its queue (so we cannot remove it while others can), and the only one actively enforcing it.
So it turns out that the people telling you to not read the code cannot even use AI to set up fair benchmarks (probably because they would have to read the code in order to do that).
You don't have to believe me, you can do your own research or ask your agent to do it for you. E.g. here is what Claude Code came back with: https://t.co/wL3VvhgshA