The linked IPPR report is worth reading. For this crowd, the section on "partial automation" is probably most important. Web dev is... up there... in terms of potential for partial automation.

There are a few important observations that the article and the IPPR report don't stress enough.

1. The jobs most likely to be automated, will be automated using technology that's inaccessible to the employees whose jobs are being destroyed.

This point is often optimistically papered over using observations like "coal miners can go to coding bootcamps!" I know a few truckers and I have no doubt that each of them could go through a relatively short coding academy for web development work if it became a "do or starve" situation. But I doubt that most of them could become much more specialized autonomous vehicle software engineers, either due to raw intellectual ability or -- more often -- due to an inability to make a substantial half-decade investment in retraining (most of these folks would need to (re-)learn a lot of high school algebra).

So just because we're replacing truck drivers with programmers, doesn't mean that the folks displaced by self-driving are somehow getting jobs that were created via the destruction of their prior employment opportunities.

2. "Partial Automation" could mean less hours worked, but is more likely to mean lower pay and more hours worked, and not all "partial automation" is equal. I.e., to destroy trucking as a middle-class profession, you don't need a self-driving truck. You just need to automate enough of the hard stuff so that anyone can learn to drive truck in a week.

I think it's useful to separate the partial automation that de-skills work (level 4 autonomy for trucks) from the partial automation that simply means less equally-skilled work (web dev). The former creates more job opportunities, but turns a middle-class job into a low-class job. The latter just eliminates from middle-class jobs altogether.