Earlier quoted context omitted.
> No youre managing a team of software engineers, one skill they have is writing. ... The product isnt the text. The product is the entire system designed to keep the text alive, functional, reasonably error free all in a relatively unpredictable environment. So, are writers just people that produce text? I think of them as people that produce systems that are explained and interacted with through text. The product o…
> I see a lot of parallels with software development. A well written story can be open to many interpretations, well written software... not so much. However, I can see some similarities in the mechanics if I squint hard enough.
Well written tools can be reinterpreted for use in many different ways. Is your favorite text editor something you use to write code, or write term papers, or to express your thoughts in diary form, even if it's eventually published online?
Our relationship to the software we use changes over time, even if the software is mostly static. In that respect, maybe software is often like poetry. A lot of the benefit is us finding your own interpretation of usefulness from it. Certain software resonates with some of us while others see little use in it. You'll have to pry Vim from my cold, dead hands, but I don't begrudge anyone their Emacs, or Sublime Text, or whatever they find works well for them.
It's a rosy, romantic view, but I pity the software engineer (or amateur code-monkey, however you identify) that doesn't feel this to at least some degree. The road is long, you might as well find some friends along the way.