I disagree with the premise - interesting but I interpret the same fact pattern differently.

The history of technology is the replacement of manual processes with automated ones.

Consider a very basic process: checkout of a restaurant.

Writing the price of each item on a sheet of paper, manually adding them and writing the total was replaced with typing in the prices and eventually with just pushing the button for the item. Paper still exists for jotting down your order but within seconds of leaving the table it’s transitioned to computer.

This has enabled lots of desirable advances- speed, accuracy, new payment rails, and increasingly, elimination of the server in checkout- you tap a credit card on a tabletop device.

Did we “forget” how to do checkout? No. We purposely changed it.

But if the internet connection goes down or the backend server powering the cash register app goes down, there is an atrophied and not-regularly exercised skill set (maybe not even trained, IDK) that has to be implemented on-the-fly and it’s slow and frustrating for everyone.

Businesses don’t exercise (or perhaps even train) this process because it’s just not needed enough to warrant the cost.

Military procurement of weapons systems is hardly the place to point to as a technological tradition. There are lots of cases where no one pays the money to keep a production process in place; the reasons are all related to shortsighted “cost savings” or failing to anticipate changing needs.

With coding today, we are seeing the same kind of shift in priorities as my restaurant example. Having humans write code in the 2020 (pre-GPT) tradition was extremely inefficient in terms of time-from-idea-to-implementation.

We’ve found a new way to do the mundane part of that task (the mechanics of translating spec to implementation).

We are figuring out how to do that while preserving quality (and a lot of it is learning how to specify appropriately).

Will we “forget” how to “build” code?

No, but the skills to generate source code by hand will atrophy just as the skills to draw blueprints by hand atrophied with the advent of CAD.

Will we find examples where someone prematurely optimized away knowledge of a skill or process, incorrectly thinking it was no longer needed? Of course.

But the productivity gains we get will be so great on average that no one will go back to doing things the old way.

There will be old-timers and hobbyists who will preserve some of that knowledge; for most it will just be a curiosity.

The West Forgot How to Make Things. Now It's Forgetting How to Code