Steve Troughton-SmithI really don't know what development on my own apps looks like, going forward. It's like going back to being Clark Kent when you're moonlighting as Superman. I can't imagine working on my existing apps like I have been with my Codex-built projects, and I'm not sure how to bridge the two ways of working. It's beginning to become difficult to imagine writing code by hand again, and it's only been a month 😐
I think part of the problem is being able to use LLMs with confidence in a greenfield codebase, vs being afraid to break anything in an established app. I am far less likely to ask it to do big things in my apps, and I'm far more likely to back out any changes it does make for fear of the repercussions. There are architectural decisions in my apps that I never would have made had I access to something like Codex at the time, and now I've made them they're too fragile and require too much to fix
Roman@stroughtonsmith A little naïve take but it proves very useful for me: test coverage. The more systems I (Codex) have covered, the more confident I am to change things. I even sometimes want to refactor something and just before that ask Codex to generate snapshot tests for many screens. To make sure not a thing looks even slightly different after it’s refactoring