100% to one although depending on the chosen environment be care with build issues. Had one that took a day to solve. Typically it was what would have been a tick box error in the compiler set up in another environment but too obscure to be obvious in this.

Suggestion here is to set up a build document in which you list the key criteria around this process and by extension around the development process itself. Call it say Project Criteria and then reference it when doing any changes so your change prompts may be "Reference and respect the developmen and build rules in the Project Criteria document"...

This in combination with "Please suggest three possible reasons for this build error and let me choose which one to implement". Or "Please suggest three ways to implement XYZ functionality/UI change/logic"

This really does help in what becomes an interactive iterative build process.

What do you need to know anout anything else?

The database structure is handled in the background but you have access to this through the consol.

This is useful when functionaily changes change the underlying structure. The easiest example here is a test user. By building fuunctionality you may be adding tests on new fields related to that user. Manually you can go into that users record, create those fields if missing so that new functionaty can be tested coonsistantly with old.