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 general they weigh the immediate harm against long-term benefits, but a lot of edge cases are discussed during the various short stories, like cases where there are only harmful outcomes. They are definitely worth a read!

Currently re-reading the Robot series, and I’m really surprised at how relevant they are right now, especially considering they were written some 70-odd years ago.

That C book was still used when I studied software engineering in the 2010s. It was even considered a ‘modern’ C book because it had been updated to include ANSI C…