The overloaded "software engineering" label can also refer to formal software engineering centered around examples of DO-178C for aviation software, IEC 61508 for railway software, ISO 26262 for road vehicle software, EAL5+ for cybersecurity related software, etc. It's somewhat unfortunate the label is also applied to CRUD websites and mobile applications, even there there is a world of difference in the various levels of formal engineering applied.
> CRUD websites and mobile applications
These can be quite intense (but, to be fair there's a ton of dross, there, as well). Probably best to avoid the broad brush.
It's somewhat unfortunate the label is also applied to CRUD websites and mobile applications,
These websites and applications can still have vast security implications depending on what kind of data is being collected.
The advertising industry has done security a huge disfavor by collecting every bit of data they can about everyones actions all the time. Adding some ad library to your website or app now could turn it into a full time tracking device. And phone manufactures like Google don't want this to change as the more information they get, the more ads they can stuff in your face.
> ISO 26262
This is only about safety. As i told to my coleagues in a former workplace: Safety first (that was one of company's mottos), quality second.