- Only be interested in increasing profit or reducing cost
- Don't care about what you do unless it conflicts with the above
- Treat people you meet as commodities
- Produce cruddy code, because "good enough" is all that matters
- Good engineering is not a "profit center"
- Don't bother keeping up with new programming languages or new techniques
The whole point of the article is to force a typical engineer to look at how most of the world perceives him, and work with that.
If you have to talk to another engineer as part of a hiring process, talk all the shop you want. If you're talking to business people, try to talk about the business advantages of what you do.
Are they, though? I can see they might be if you're in consulting (as the author of this post appears to be), but I've never heard of an interview at somewhere like Google or Intel that wants to hear you talk about Providing Value; they want to know your technical skills.