Earlier quoted context omitted.
How does programming fit into this? It feels a bit in-between. On the one hand, you tell the computer what to do, in a way that feels similar to Type 2; on the other hand, you actually have to do the work of programming, which feels much like Type 1, except you're not moving physical matter around, but stuff in 'concept space'.
In all seriousness, I've long thought of what I do as moving electrons around, getting pits onto CDs in the right place, things like that. Whatever I do in, say, C++-land, is a means to those ends. An intermediate step. I arrived at that way of thinking after trying to define 'work', and deciding that it always consists of moving matter around (transporting it, putting it into a desired configuration).
When I look at the end results of work, I come to the same conclusion that indeed it ultimately consists of reconfiguring matter. That's what we need to do to reach whatever goals we have. Maybe the conceptspace work maps to the levels of intricacy of the end-result matter configuration, i.e. the more complex, precise thing you want to get, the more energy you need to expend on thinking rather than arranging atoms. It's easier to move a ton of bricks from one place to another than to design a microprocessor.
So I guess that ultimately I agree with your comment.
(disclaimer: writing this after two beers)