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.
replies(2):