Re:Ask HN: How to deal with shipping AI-written code you don...
by blackrainbowlab on Monday October 19, 2026 @06:44PM
(#50159042)
My workflow involves research, then technical design documents, then implementation, and a very heavy emphasis on E2E testing.
[ Parent
| on HN ]
Re:Ask HN: How to deal with shipping AI-written code you don...
by narmiouh on Monday October 19, 2026 @09:41PM
(#50160335)
how often with a structured approach like this, you end up with large completed features that don't have many bugs?
Re:Ask HN: How to deal with shipping AI-written code you don...
by blackrainbowlab on Thursday October 22, 2026 @09:37AM
(#50195151)
Pretty often, especially once you have the project becomes more established. I'd say 80-90% of the time for me right now. I lean very heavily on E2E testing.
I have 2 major products I'm working on:
- a db written in Rust that is 500% faster than SQLite, and has 100% parity. https://inillucent.com/
- an agentic ide written in Rust https://unluminous.com/
Now that they are both well established, I'm able to ship new features quickly, and with very few bugs.