Re:Why developers need to be able to identify technologies w...
by swsieber on Monday June 25, 2018 @01:59PM
(#17394332)
To build upon your comment:
It's not because older technology is inherently better, but it's because if older technology is still relevant, it's survived the "will it be relevant in the future" test once before.
Re:Why developers need to be able to identify technologies w...
by flukus on Monday June 25, 2018 @09:42PM
(#17397293)
> That's called experience. This is the reason why senior developers are normally paid more and make the important decisions.
The problem is we obtain that "senior" title long before we have this experience. Then when it's finally deserved (the 10+ year mark) the pressure starts mounting to move into architecture/management roles. And let's not forget the "old man can't keep up" that's always been rampant.
The industry as a whole seems to consider experience as a liability.
Re:Why developers need to be able to identify technologies w...
by mgrennan on Monday June 25, 2018 @02:06PM
(#17394379)
As a person with 40+ years experence (Yes I started with a 4004) I aggee.
Change is constend and the advancement of more and more complex systems is inevitable. Most of these is good but some with issues. The quote "A sufictly advanced technology is indistinguishable from magic" describes an ADVANCED tech.
I believe it is the speed we are developing the tech that is the problem. We are more often then not ignoring the wisdom of senior developers.
And what the article tells is that you should actually get interested in what you are doing, if you want to become experienced and not just old. That should be common sense, but I guess it is worth repeating from time to time.
However, if you don't have 30 years of experience, ranging from coding on a C64 to modern JS frameworks, the Lindy effect (older technology tends to stay longer) is a good shortcut.