It seems endemic to software to me that people constantly want to brand things as "engineering" that aren't. They always want to call it engineering because it sounds better but they don't want to do nearly anything associated with engineering - rigorous process control, systematic documentation, specification of tolerances, resource usage etc etc.

What's described here is mostly a list of barely disguised tips, tricks and heuristics. It's all fine until someone wants to put it in production and suddenly a "real" engineer has to take over and do the actual engineering.

(and yes, I'm old - and grumpy!)