4 ms·
Not so true. If any, technology only got less innovative, which is evidence that the field is stagnating. For example: 1) docker / container - an OS process (
by streetcat1 7y ago
Not so true. If any, technology only got less innovative, which is evidence that the field is stagnating.
For example:
1) docker / container - an OS process (circa 1960).
Basic OS design (os/360) did not change in 50 years.
2) Computer architecture (Von Numan) did not change in 50 years.
3) Basic DS and alg (not ML), did not change in 50 years.
4) Programming lang (C based).
5) Database/SQL (50 years)
The only things changing today are (as you mentioned):
1) JS frameworks. but not so much as react won (probably vue js)
2) ML. Here again, most of the work is abstract by pytorch/tensorflow.
3) cloud-native app design. This is a major shift.
However, in parallel, there was a massive productivity boost due to free tools / cloud / open source. So today's programmer should be equal to a team of 10 , 10 years ago, and a team of 20 , 20 years ago.
- NotSammyHagar 7y agoSure, core concepts like vms are still around but the practicality and common usage and comfort and ability to understand how they can be applied (like containers) does change, and does affect your ability to get jobs, or at least interview well. I'm also older, over 50, and I'm frustrated at all these people who are similarly experienced and complain that companies don't recognize their abilities. You have to update your skills and be able to talk about the current stuff. You are foolish if you don't practice before an interview. Before I switch jobs, I take it seriously and do something like 1 hour practice every day for a month. I look at current software engineering topics (I'm usually wasting time on hackernews so I'm up to date on the latest gossip). You have to try, people!
- streetcat1 7y agoAmen to that!
- mikekchar 7y ago25 years ago, if you knew C++ and were and expert in MFC you could write your own ticket. Now I know a lot of unemployable MFC experts. When I first started I was encouraged to learn Cobol, APL and DB2 because that's where all the money was. These days I meet people who think that they Ruby on Rails with a bit of React thrown in is going to last them a lifetime. My point is that becoming an expert in a particular language, framework or technology and expecting it to pay you for your whole career is a recipe for unemployment eventually.