chris_fullcycle

The problem is when you have the wrong team. It's way too easy to partner with the wrong person, and not even know until years later.

I'm finding that yes, it takes longer on my own, I can have AI do much of the stuff for me that I don't want to do.

If the code works, then is the technical debt a problem? AI can already write the code better than most developers, it just may not be doing so at this time because of the person prompting it. At some point, either somebody will get there hands on it who knows how to direct their AI to clean it up, or AI will get good enough on its own to simply do it.

I've built a bunch of projects with Claude Code, and the flow that works for me is planning as much as I can up front. Once I'm confident we've caught most of the requirements and the likely gotchas, I let CC run and just check back periodically to approve continuations until it's done and ready for me to test. One project at a time keeps me in a flow state.

A more exciting attempt the other day: I fed CC a PRD and ui-spec I'd drafted with Fable 5 (no reason, I just happened to be on my phone), told it to auto-approve commands, and let it fully build and test the project in Chrome overnight. I woke up to a mostly-working app ready for me to QA. Skipping the whole build cycle and going straight to watching it come together during testing was genuinely great.

The one thing I'm still figuring out is the trust side of fully-unattended runs like that. Curious how others are handling auto-approval when nobody's watching.

While it can be productive, I never feel like I'm in a flow state doing this. The general context switching can actually be a bit draining to me.