That's the funny thing. I definitely fall into the 'medium level' dev group (Coding is my job, but I haven't written a single line of code in my spare time for years), and frankly - I really like Copilot. It's like the standard code-completion on steroids. No need to spend excessive amounts of time describing the problem and review a massive blob of dubious code, just short-ish snippets of easily reviewed code based on current context.

Everyone seems to argue against AI as if vibe coding is the only option and you have to spend time describing every single task, but I've changed literally nothing in my normal workflow and get better and more relevant code completion results.

Obviously having to describe every task in detail taking edge cases into account is going to be a waste of time, but fortunately that's not the only option.

They'll probably just have to be sent as a parcel in stead, using PostNord or one of the International carriers. It already costs about the same to send a parcel (up to 1 kg) as a letter, and service and shipping speed is infinitely better anyway.

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...