One need look no further than the O'reilly book on Microservices. First chapter I believe. We call ourselves "engineers" but the truth is, real engineers have real consequences when their designs fail. (buildings fall, bridges fall, etc). It's not a unique take. Now I'm not going to argue about engineering vs developing vs programming as that opens a massive can of worms.

What a weird criteria to define engineering - consequences!

It's not my designation to give. An "engineer" actually needs rigorous certifications, backed by a certain education.

If I do have an engineering degree in informatics, then when developing code I'm doing engineering - right?

"rigorous certifications" - just a degree... not so rigorous

>> Like if we're not there entering the "numbers" 4 6 15 16 24 32 every 108 minutes, the entire business is going to crumbl

> Never I have encountered an engineer that thought that.

there are people all up and down this page saying effectively just that. well i guess i'm assuming most of these people are engineers in the software sense of the word.