[shalmanese]

> or if you prefer, there is a cycle between the two states

Yes, what I mostly emphasize with this mode of thinking is that the act of building software is primarily there to transform people (you try a thing, it doesn't work like you think it would, that inspires you to try another thing) and the software at the end of it is largely a byproduct.

If you have the right people-state, producing the software is trivial, it's how do you port the right knowledge into their brains in the first place and and software should be just another tool in your toolbox towards that aim.

[mathgeek]

Perhaps sometimes and in an ideal state, but most folks who code learn a lot and make a lot of design decisions while producing software.