2 ms·
> huge collection of skills I've [been] developing One thing I've noticed about that is that if the skill was developed more than about 5 years ago, it's frown
by commandlinefan 7y ago
> huge collection of skills I've [been] developing
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".
- 6gvONxR4sf7o 7y agoThere are different kinds of skills. Postgres vs spark is one kind. C++ vs python is another. Statistics vs networking is a third. The top of the skill pyramid changes quickly, but the fundamentals change slowly. A tool might be outdated while the solution it implements is not. (But “ooh shiny new thing!” can still be a problem)