> You start saying 'software engineer' and end with programmer. Clarify your terms.
Eh, it snuck in there. I specifically changed programmer to software engineer in multiple spots to disambiguate it because I was talking about "programming" as an act distinct from applied CS. I missed doing so at the end.
> There is a huge difference between willing to take on liability for your faults versus slinging code.
Based on your assumption of what I meant, it sounds like you have something you wish to express on this point. Perhaps you should do so in more detail?
"Engineer" means someone who is licensed and is professionally and legally liable for the work they produce. Those who are licensed engineers often feel that the term "software engineer" cheapens the term because software folks are not licensed and not held liable for their work (and in some places, it is illegal to have "engineer" in your title without a license). On the flip side, software developers need a way to differentiate titles between the folks who copy-paste code from Stack Overflow with little understanding and those who build well thought-out, robust solutions. Folks sometimes put this on a spectrum from script kiddy, programmer, developer, to software engineer. Perhaps a new term is needed...
Eh, it snuck in there. I specifically changed programmer to software engineer in multiple spots to disambiguate it because I was talking about "programming" as an act distinct from applied CS. I missed doing so at the end.
> There is a huge difference between willing to take on liability for your faults versus slinging code.
Based on your assumption of what I meant, it sounds like you have something you wish to express on this point. Perhaps you should do so in more detail?