Peter KaminskiI'm having Claude Code build HangarWiki, a git-native dream wiki engine: live, editable on the web, your own replacement for github (Forgejo or Gitea), plays nicely with MarkPub + Obsidian+Git. Extremely early, basically spit and baling wire: https://github.com/peterkaminski/hangarwiki
John Abbe (aka Slow)@peterkaminski I assume there is quite a lot of back & forth, and that Claude is not the one who initiates new versions, so wouldn't "working with" be more accurate than "having" ?
@slowenough, Claude Code is doing 100% of the coding, 95%+ of the architecture decisions.
CC does like to check in frequently, but mostly light check-ins, deciding which feature to do next or me doing a little bit of user review and giving feedback.
(A nice way to get out of its way was to ask it to set up a headless browser; now it can do a lot of the user review checks itself.)
Saying I'm "having it build it" is quite accurate; I'm a hands-off manager and coach, basically.
@peterkaminski Something tells me I would quantify the architecture decisions made *rather* differently than whatever method you are using, but I understand the relatively small amount of time (compared to previously available options) you are having to spend giving your architecture input. :-)