I find this strongly depends. I agree with the article, but this sentence seems to generalize it a bit too much. As a developer, I'm bottlenecked by ideas, not by coding. And I don't mean "make a site kinda like eBay" ideas, but ideas like:
"How do I optimally distribute quality across a video frame to best approximate the human visual system?"
"How do I measure video quality in a manner that takes into account the human brain's dislike for certain types of artifacts?"
"How do I reorder the operations in this 2D frequency transform to avoid having to transpose the data?"
The answers to these are certainly "ideas"--but they're ideas that are far harder to come up with than their implementations. While "make a site like eBay" takes a few minutes to come up with and a few months of development to implement, something like the above might take an hour or even as little as 15 minutes to implement, but the ideas are few and far between.
Here's the anecdote for the third of the above:
Developer1: I found a way to make this frequency transform a whole lot faster, but I'm not allowed to say yet because my university won't let me.
Developer2: Wait, that can be done faster? I didn't think it could be done much faster. If it can, it must mean there's a faster way to...
30 minutes pass
Developer2: Here's a patch, it makes the transform 60% faster.
No speed advancement had been made in that extremely important and often-called function for over 6 months--and it took only about 30 minutes to make it that much better merely from knowledge of the fact that it could be done better.