- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
I remember being taught Model-driven development using Eclipse as part of the software engineering study back in the early 2000’s. Even as a student it was painfully obvious that you’d spend an awful lot of time trying to work around annoying limitations in whatever tool was used, rather than just writing the code yourself. The parallel to vibe-coding seems rather obvious.
In order to replace programmers with vibe coding, stakeholders would need to be able to describe their requirements accurately.
And then they’d need to be able to verify that the code actually meets these requirements. That might even necessitate specifying these requirements in some sort of a formal language…


