It's not clear to me what you mean by software. Software is just a tool and writing software is also just a tool, more often than not, not that interesting in itself. Solving problems using software is the goal and can be realized with various ways, like those low-code solutions you mention.
This is why I'm becoming more and more unhappy about calling myself a programmer. It just doesn't have that "problem-solving using computer technology" ring to it.
>>> It's not clear to me what you mean by software.
>>> This is why I'm becoming more and more unhappy about calling myself a programmer.
Patio11 wrote about this and it is a good piece of advice - essentially it means sell your service (labour) as the value it can produce not the time it takes. This is a common piece of business as ice and is dry sensible.
But the main point is, as a software coder / developer / programmer, for most business areas software provides excess leverage and so the amount of value you can produce is greater than fir same time of a non-coder.
However to do value based charging involves other skills - negotiation, domain knowledge, lead generation and lots of meetings that go nowhere.
But even if you don't do the latter part that software still can produce outsize leveraged returns for effort input. You just won't get a cut :-(
That does not mean you did not help create the value
Agreed. Programmers code. Developers build software. Most software engineers work under a developer (business subject matter expert, slash, product owner) as programmers.
The person who envisions and specifies the features is the developer. The person who translates those into code is a software engineer or programmer. Sometimes they are the same person. In the corporate world, rarely ever.
In the corporate world if the software engineer can capture and document a business domain's processes then they are effectively taking the job role of developer from the product owner. Most people are comfortable leaving that in the hands of someone else and making it "their job." Engineers have the chance to take power but rarely do because they get caught up in the weeds of trying to covert a trickle of requirements into code because...agile. Developer Hegemony, when are we going to wake up?
This is why I'm becoming more and more unhappy about calling myself a programmer. It just doesn't have that "problem-solving using computer technology" ring to it.