3 ms·
The point is to work at the sweetspot of emerging language/high pay and then get out once the framework decision level bugs start emerging. Then come back as a
by kkarakk 7y ago
The point is to work at the sweetspot of emerging language/high pay and then get out once the framework decision level bugs start emerging.
Then come back as a consultant in 20 years at the intersection of high pay/no one else can figure out how to fix the software.
If you're working with Java you're mostly in medium pay/tearing hair out coz of legacy issues-which you WILL have because a Java shop never COMPLETELY moves to the new thing. Not a fun place to be.
- abraae 7y agoExcept that Java is that 20 year old thing, and it has stood the test of time, it's not the new COBOL. I learned vi about 30 years ago, Java and SQL over 20 years ago, and they're tools I can still use every day to get stuff done.
- simion314 7y ago>If you're working with Java you're mostly in medium pay/tearing hair out coz of legacy issues-which you WILL have because a Java shop never COMPLETELY moves to the new thing. Not a fun place to be. I am working in the present on Web tech, SPAs, but you know what, it sucks even if is the cool thin, the project was started with angular1 which is no longer the cool thing, it uses ES5 and gulp(no longer the cool thing), the backend uses Silex(a PHP framework that is not that cool) ... The only cool thing I assume is to start new project in the this month cool shit and then after 1 year move to the new shiny and let people like me maintain your inexperienced code in the experimental shiny thing of last years.