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.
Comments
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.
The discussion is about founding a company. You're talking about being a software engineer.
I'm really not. I understand the context.
@roel_v yes. Also a very relevant one to the conversation. See my profile.
Sorry to be 'that guy', but have you ever build a (successful) business?