I really don't want to have that argument yet again. However I hold an engineering degree and a computer science degree. Software engineering is very much engineering. Engineering is the art of tradeoffs and balance. Using a lighter weight, but more expensive steel in a structure to place less load on the foundation is an example of a tradeoff in Structural engineering.
Once you get beyond the most simple code you are practicing tradeoff and balance. You can use a simple, memory intensive algorithm, but you need to understand if you have the space to use it. You might be able to develop software in 1/2 the time if you take a basic approach, but it won't scale.
I don't know if you develop software or not. Regardless think more deeply about what is involved in engineering.
You seem to have a peculiar notion of what makes up engineering. Data informed tradeoffs, math driven analysis, and deep knowledge on your field are keystones of engineering. These are also the keystones of Software Engineering which is what I practice.
Once you get beyond the most simple code you are practicing tradeoff and balance. You can use a simple, memory intensive algorithm, but you need to understand if you have the space to use it. You might be able to develop software in 1/2 the time if you take a basic approach, but it won't scale.
I don't know if you develop software or not. Regardless think more deeply about what is involved in engineering.