I don't think you are making a correct analogy here. If you build software and that's what you enjoy, then build software, don't build audio systems or design furniture. The actual industry you build software for... well not as important, as long as you are building software as that is where your passion is.
Your day to day activities for your work are very similar if you are building software for a call centre or building software to manage coffee distribution (I am just assuming you might like coffee here). The industry plays a very small part in what you do, but it greatly impacts the chance of success.
I don't think you get the idea. "Building software" by itself doesn't mean anything; software is made to have some utility.
The parent is not talking about code, if you're starting a business, the industry defines a major part of what you do.
I disagree. Building software does mean something, it is what you are doing every day. If I am building software, I am writing code, testing, deploying and designing user experience workflows. All of that is the same no matter which industry my end users are in.
Sure your product is made to have some utility, but it doesn't have anywhere near the impact on your day to day activities that people think it does.
The industry defines a major part of what your software does, not as big a part of what you do. I think it's an important distinction.
Your day to day activities for your work are very similar if you are building software for a call centre or building software to manage coffee distribution (I am just assuming you might like coffee here). The industry plays a very small part in what you do, but it greatly impacts the chance of success.