Just How Bad Would an AI Bubble Be?

This article presents the apparently widespread, but incorrect and, frankly, boring view that "coding" is the bottleneck in development. The following statement summarizes this view best:

> Many knowledge-work tasks are harder to automate than coding, which benefits from huge amounts of training data and clear definitions of success.

which implies that "coding" is not knowledge work. If "coding" is understood as the mere typing of requirements into executable code, then that simply is not a bottleneck and the gains to be had there are marginal (check out Amdahl's law). And if "coding" is to be understood as the more general endeavour of software development, then the people making these statements have no fucking idea what they're talking about and cannot be taken seriously.

It's a familiar approach. "We have a ton of tickets, each pretty simple, but not enough hands to devote to all of them." It usually turns out that the "pretty simple" bears a lot of weight there, and assumes more than meets the eye reading the ticket.

so was the article conflating the two or was it just pointing out the software developer roles typically have many hats that can and sometimes are held by other in the process. ie. systems analyst, business analyst, architect, designer, PM, QA etc.