This seems like a recipe for bad code I dunno. How would someone using this app test as they go? Agentic coding sorta works for me because you can stop and test each iteration and pinpoint where something has gone wrong. Example: I ask for a tweak, it give me 20 lines, I test for the intended behavior and keep working on those 20 lines until I'm happy with the reliability/effects of it. But that loop itself requires…
What model are you using? I can use Claude Code's remote control on Opus 4.8, have it implement a meaty feature, talk through edge cases, ask it to posit potential interactions we want to be careful of, have it write a plan and expand tests for surrounding areas, ask it to implement, ship that increment to testflight, then experiment with it on my phone - without being at home. My only limitation is that I like to cl…
I understand the feasibility of this and sometimes in my lazier moments I skim the code changes and trust automated/manual testing to validate changes, but to just like... you don't even see what it did?