137 karma · joined November 7, 2017
Being able to get rid of (1), either through automation or delegation, allows you to go to (2). If you’re stuck on (1) for too long, it’s better to leave.
The key here is what are you taking responsibilities and decisions for. Senior engineers take decisions which consequences will be apparent in a year or two. If productivity increases to the point where features that take months to deliver take days, the decisions made _currently_ by senior engineers can be taken by fresh graduates.
There’re still going to be senior roles, but their scope will be much bigger and expertise sought will be different than what senior engineers do currently. No one will hire a senior engineer just because they can architect and deliver a scalable SaaS product on a short timeline.
Engineers who learn and adapt will be fine. Engineers who dropped learning the moment they graduated from college… not so much.
The role of junior software developers will not be needed, just as we don’t need people doing multiplication by hand.
The bigger issue imho is companies using biometrics as a secure authentication, but at least in USA that’s going to be no worse than SSN mess.
[1] http://www3.weforum.org/docs/Global_Social_Mobility_Report.p...
That’s a reach. Global interconnected private enterprise was widespread before both ww1 and ww2. We haven’t had a war between major global powers after ww2 because of MAD and Pax Americana.
While Apple policy seems heavy handed and completely out of touch, I hope situations like this will bring back physical controls to devices.
Much better motivation is love for a process, in ship building example, ship engineering with management supporting career development.