Old, but fun read that argues that today’s programmers are not like typical Engineers and shouldn’t really call themselves that as Engineering requires certification, is subject to government regulation, bear a burden to the public, etc.
Old, but fun read that argues that today’s programmers are not like typical Engineers and shouldn’t really call themselves that as Engineering requires certification, is subject to government regulation, bear a burden to the public, etc.
I’ve always used “software engineering” to refer to the other stuff that comes alongside actual development, like version control, testing, CI, debugging, code review, release management etc.
You’ve forgot the actual “engineering” parts which distinguish programmers from engineers: requirements engineering, software architecture and complex problem solving