PREACH. I have no idea why THIS has become the standard for illustrating model capabilities. It's endlessly frustrating when that was the initial objective for all these models, but, became increasingly clear over time that none of these models were ever capable of getting the desired output for complex software on the initial prompt.
The reality is:
- business rules change
- ideas for improvement may arise from the initial prompt
- updates to submodules/functions/configs/secrets are BLOCKERS
... etc.
One shot prompting for the expecations of complete software is seemingly more and more a show of incompetence of the use of this technology. It's like trying to make my toddler eat a ham sandwich from the peanut butter & jelly I put in front of him.
This sounds like a process + human problem, not a technology problem. To me, it sounds like your team lacks discipline and competence. Sorry bud, going to categorically disagree with your sentiment that git is terrible.
I FEEL this. It's empowered lazy devs to defer thought and accountability. To some degree, I understand. It softens the imposter syndrome feeling one can get. But, I see it as a character barrier; not a moral one.
Ah, yes. California. Where large swathes of costal areas hover between 60ºF and 80ºF. We are talking about Nevada the weather of locality matters and where it can be supremely hot.