The conversation led to a new light bulb . I am sure most devs have already figured it out !
# New Dev /Test cycle with AI
## Specs
Describe well what you want - Let AI create the specs - Read the specs - ask for changes - let AI rewrite . Run the specs with experts. Ask questions. Narrow the scope of first version - Spend at least couple of days .
## Build / Deploy / Test
All these are rolled into one because build and deploy is pretty much ten minutes job. The key thing is TEST. This is where you want to spend time - Test well.
## Spec Rewrite
Every time you encounter a bug , don't run back to AI to improve your code . NO ! Instead append every bug in Spces . Basically testing and spec rewrite go head in hand . Each time , have your model rewrite the specs with a separate section of say POETNTIAL BUGS.
## LOOP
Basically run the cycle at least 7 times . Because it took GOD 7 days to build the world. It was not separate things being built daily.. It was prompt getting updated - 7 times :-)
## Backup
Only thing to back up in this cycle is the Final Specs .. That is where #nostr comes in - store your specs as a long text event !
The question is how do you learn !
This is where version management comes in ..
Don't waste your time , reading the first code . Rather have git give you a diff between successive version . Now that you have a baseline of code , and have a vantage of bugs , check how AI fixed those bugs ... You don't need to know the coding language , or architecture ... The knowledge is built into the change . Read the comments and add more comments ..
Git diff is your path to knowledge .. once you gone through seven cycles of diffs ... I think , you will be able to maintain the code .. without having to run back to AI ..
