Strongly disagree here. The taste-skill gap still applies even when there's no mechanical skill involved. A lot of amateur music production is entirely "in the box" and the taste-skill gap very much exists, even though it's trivial to e.g. click a button to change a compressor's settings.
In programming, or more broadly application development, this manifests as crappy user interfaces or crappy APIs. Some developers may not notice or care, sure, but for many the feeling is, "this doesn't seem right, but I'm not exactly sure what's wrong or how to fix it." And that feeling is the taste-skill gap.
If you don't know what sound you want to hear at all, that's undeveloped taste.
If you know what code you want to type, but don't know how to use a keyboard, that would be a taste-skill gap.
If you don't know what code you want to type at all, that's undeveloped taste.
Ira Glass is a writer. Do you think he meant the taste-skill gap was when people couldn't physically write the words on the page they wanted?
You either know what you want to write or you don't. If you hate the words you wrote, write something else. If you don't know what you want to write, that's undeveloped taste, not a gap preventing your from expressing your good taste.
The taste-skill gap emerges when you intellectually recognize what a quality creation would be, but are physically unable to produce that creation, and judge the creations you are physically capable of producing as low quality
The oft cited example is drawing a circle. Everyone knows what a perfectly round circle looks like, but drawing one takes practice.
It doesn't take practice to type code. If you know what code you're supposed to write, you write it. The problem is all in the taste step, to know what code to write in the first place.