How is this different to the person or team who wrote the code leaving the organisation. It's the same thing, its not having the institutional knowledge of the codebase because you can't get it out of the model that made it. So you need to create ways of maintaining that knowledge as its being developed.
Then when you say building the constraint before work begins, don't you mean just understanding the end of result before you build it. Actually identifying functional and business requirements? These aren't anything new in the AI world, they're engineering concepts that stood true before but were often ignored even in an non-AI world.
This article might be helpful for the vibe coder who doesn't have a career in software engineering, but its not news to the field itself.
Just tonight I decided I needed a specific app to interface with Gemma4 that would allow renaming of folders of files. I went to create a blank workspace to start and it said the folder name I chose already existed. When I opened it there was the entire app I had built a month ago, laid out a huge UI and debugged it all. I just accidentally forgot the whole app o_O
In fact, a couple of times I've opened old pre-AI-era code and simply asked the AI "Write an MD that explains what this app does, how to use it and how it is designed."
