Ask HN: I had Codex and GPT 5.6 Sol running for 12 days, 870k+ LOC. Now what?

1 points by iagooar 20 days ago | 3 comments

For the last 2 weeks I have been running Codex + GPT 5.6 Sol Ultra non-stop for almost 13 days, working on a huge extension to my SaaS product / business. It used 502,122,866 tokens and created over 870k new LOC.

I have done AI coding of huge features in the range of 50-60k LOC before, which were massive already, we managed to ship them and actually deliver value.

I know this sounds borderline ridiculous, but this time I don't know what to do.

What are the next steps here? It is obviously impossible to review, but it is almost as impossible to actually test. I had put A LOT of work into planning and the workflows and features were spec'ed very precisely and with lots of care and analysis. So far I have only found cosmetic issues, the entire core of the application seems to be working just fine.

I have thought about starting with a user manual / knowledge base for it, to capture the features and have plenty of documentation. But then what? Launch it to production?

Have I passed the threshold of what is humanly possible to do with AI coding, or is there any hope?

proc0 20 days ago |

You need to be able to iterate and extend the codebase, as well as grow it to 100K+.

Personally, I would focus everything on making changes easy to make at large scale. Typically with a human programmer this comes from designing and architecting and coming up with clever solutions that allow new features to be built faster even with a lot mroe lines of code. Maybe AI can do that, but I think it's uncharted territory because the biggest companies use AI with established codebases.

verdverm 20 days ago |

Trash bin? ~1M LOC for what? If you cannot review or test it, then why would you trust it?

This is why it's better to stay human in the loop during the process. Sounds like you don't think it should take 1M LOC. It's likely your garden variety slop, even if it "works". Avoid the sunk cost fallacy, Ai lets us throw away more experiments because they are "cheap".

iagooar 19 days ago | |

So far every single test I've done has worked correctly, I put a lot of work and time into preparation and planning, each workflow was designed, researched and optimized before implementation. The specification was already a massive document, so it is not a one-shot by no means.

I might check it and if it turns out to just be extremely bloated, I will re-write it from scratch. But before I do that, I might as well give it a chance.