I used my $100-per-month Cloud Code subscription. It was enough to build the compiler from scratch. Although the subscription also allowed me to work on other projects simultaneously, the methodology optimizes resource usage—an important aspect to demonstrate as well. That is why I chose to create a C compiler.

Don't get me wrong. I'm here because I'm interested as well.

- Wall clock time is three months(?)

- Cost $300 possibly shared by other projects(Does CC provide credits or a token measure?)

- How much of your own time was spent interacting with Claude and/or thinking in parallel to his work?

- Did the service go down during those three months(including subpar service by a substitute "flash" model)?

Yes, it involved seven weeks of work using Claude Code sessions—from July 25 to September 14, as indicated by the repository commits.

The total cost was simply the recurring monthly subscription fee. I wasn't granted any extra credits by CC; although I occasionally hit my weekly usage limit—partly due to consumption from other projects—I would simply wait a few hours before resuming work.

I spent six to eight hours a day interacting with the session, and whenever I had the time, I dedicated even more hours to it, as my goal was to get the job done. During the final days, much of the time was spent waiting for regression tests to pass so I could proceed with debugging.

The service remained active throughout the entire seven-week period. I consistently used Opus 4.8 to maintain model consistency during development.

That provides a much clearer picture, thank you.

Thank you for your interest in this topic.

I tried to post as "Show HN", but HN restricts Show HN for new accounts.