Expectations vs. Reality at Work

One thing I've noticed about that is that if the skill was developed more than about 5 years ago, it's frowned upon, if not outright rejected. I'll be presented with a problem that's a perfect fit for, say, a relation database, or a cron job, or a shell script - but the simplest solution is rejected as being too archaic. Instead they insist on some workflow management tool, or Spark, or a GraphQL database that doesn't fit the problem, just because it's newer and must be "better".

All the crap trickles down and infests everything, not just IT.

Think about it.

While they're certainly not always true, they're conditions that one should be aware of the possibility of. One particular anecdote in the article:

> Disagreements are often about the underlying fundamental assumptions and world views that are so core to a person he can’t articulate them, any more than a fish can see water.

Has been a fundamental component of my career. I've spent time working in virtually every major business function (from marketing to software engineering teams), giving me a very well rounded understanding of the (often very) different lenses that different types of people and different job functions view things. Now, I spend more and more time getting pulled into client servicing work, as I'm able to jump down the rabbit hole with any stakeholder that ends up in the room, using the same viewpoint and thought process they do to assuage and concerns they have.

Different people expect different things, so the expectations in my post can't obviously be interpeted as universal.

> Many of the “reality” parts are not always true, too

Which is why they're phrased as "often" or "sometimes" or "can happen". Not "always happens". If I've forgotten to add such a qualifier somewhere, please let me know, and I'll fix it.

Is your anecdotal claim a valid counterargument to another person's anecdotal claims you disagree with?