Science

Cool. II've noticed this, and I think people often go for the most expensive solution, with the idea that it must be the best one.

People think that the amount of stuff you built is a measure of how much work you've done.

It's really striking when you look at people with engineering skills/training, they want to reduce things down to the simplest, most efficient form. But everyone else just wants to add more stuff onto the stack.

The people who end up in jobs with administrative power are rarely people with engineering skills.

This reminds me of UNIX where much of the code was basically "removing things from multics". Or, in case of C, removing everything from B and then re-adding it. Possibly this was a subconscious workaround.

Removing is hard, maybe because it's less intuitive that the already present features aren't "removed" in the subtractive process?