When I read the title I was curious what definition of “engineering” would be in play. I wouldn’t call the process around programming and problem solving “engineering”. I’d just call that “process”, or “overhead”, or (when feeling like speaking plainly, “inefficiency”). Who loves that? It’s necessary, but loving it certainly isn’t necessary (or even good?).

I’d call the problem solving that balances technical, human, economic factors and produces great code “engineering”. Knocking out code on a whim less so.

My message is just be careful who you’re speaking to when saying you don’t want to engineer — I’m my book you do.