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.
There is a bog difference between a software engineer and a software developer/programmer. In the same way there is a difference between a civil engineer and a builder.
A software engineer is the one who scopes the project. They define the feasibility, the limitation and exeptions, the tools to use, as well as costing and time planning and management.
The programmers are the ones who work to this scope and utilise the specified tools and technologies to create the product.
I have a degree in software engineering and all of this was covered. From writing scoping documentation, to time and costing with Gantt charts. This is the actual difference.
You’d think that’s how it is but in reality they list software developer roles as software engineer just because they think it sounds better.
Yeah, fair enough that might be what HR/recruitment does. It doesn’t mean that there isn’t a difference though.
Also I’m not sure if that is more of a US thing maybe? I see most roles in Australia listed for “developer” not “engineers”
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