31 ms·

Veterans have seen technologies come and go. If they were keen to hop on every new technology that came out during their career, they'd literally never get any

Veterans have seen technologies come and go. If they were keen to hop on every new technology that came out during their career, they'd literally never get anything done. The risk of adopting a technology that will fail high and the results can be disastrous. It might be seen as stodgy to pick Java along side a relational database for a brand new application over the latest JS hotness plus NoSQL. But we know that Java is going to still be around in 20 years, we know the language and architecture can do what we plan, and is easily able to expand and scale as the product grows. We know what deployment, integration, maintenance, etc looks like. What young developers don't see is the long, long, long line of failed technologies that were hot, then faded it obscurity. It's very hard to bet on winners.

nkkollaw 7y ago
This is exactly how it is. Unfortunately, it seems to me that new devs have to always bw kept entertained and know/care very little about the business, and would rather make the company tank and have fun experimenting and move on, than get the job done. Maybe I'm getting old.
- deleted 7y ago
  [deleted]
parliament32 7y ago
It's a "big picture" thing. It's not necessarily about age, but rather experience. A dev who's been in the industry for <5 years simply hasn't seen the sheer amount of shitty tech come and go over the years.
boznz 7y ago
Agreed. Learn something well and if it isn't broke don't change.
doggydogs94 7y ago
If someone is paying me well to learn a new technology, I have no problem taking it on.
jesterson 7y ago
Came here to write this, but @mywittyname did it better. Young colleagues have tendency to use framework/technology as a solution to a problem, while it's always an instrument to reach a goal. Older colleagues can assess solution for multiple point of views - security, long term manageability, integrability, support, etc. Younger colleagues are focused mostly on narrow field due to lack of experience. Obviously it's generalisation so take it with a grin of salt.
jerome-jh 7y ago
Agreed here too. Older devs also love new tech. Sometimes you can just pick up the new idea and adapt it to old tech.
oromier 7y ago
I don't see javascript being obsolete in the next 20 years too.
- vkoskiv 7y ago
  But that hot new JavaScript framework/library is long gone in 6 months time.

nkkollaw 7y ago

This is exactly how it is. Unfortunately, it seems to me that new devs have to always bw kept entertained and know/care very little about the business, and would rather make the company tank and have fun experimenting and move on, than get the job done. Maybe I'm getting old.

deleted 7y ago
[deleted]

parliament32 7y ago

It's a "big picture" thing. It's not necessarily about age, but rather experience. A dev who's been in the industry for <5 years simply hasn't seen the sheer amount of shitty tech come and go over the years.

boznz 7y ago

Agreed. Learn something well and if it isn't broke don't change.

doggydogs94 7y ago

If someone is paying me well to learn a new technology, I have no problem taking it on.

jesterson 7y ago

Came here to write this, but @mywittyname did it better. Young colleagues have tendency to use framework/technology as a solution to a problem, while it's always an instrument to reach a goal. Older colleagues can assess solution for multiple point of views - security, long term manageability, integrability, support, etc. Younger colleagues are focused mostly on narrow field due to lack of experience. Obviously it's generalisation so take it with a grin of salt.

jerome-jh 7y ago

Agreed here too. Older devs also love new tech. Sometimes you can just pick up the new idea and adapt it to old tech.

oromier 7y ago

I don't see javascript being obsolete in the next 20 years too.

vkoskiv 7y ago
But that hot new JavaScript framework/library is long gone in 6 months time.