The job is to automate the enterprise, keep things safe and reliable, and make money for the company.
It was never about software. That was just the means.
Even in the software era, fads developed and tech stacks changed frequently. Now it's just moving a hundred times faster.
You need smart systems thinkers to do this. That's the role. Be smart in managing processes and complexity.
I'm not going to give coding interviews anymore, but I am going to give architecture, systems design, and SRE interviews. People still need to know how not to fuck up a database and how to design scalable and resilient systems.
The number of people who never seem to have understood what software and IT is in most companies is eye opening to me. Your job was never really to "write code" - you were always automating things.
That the field got somewhat stuck for a couple decades seems to have made many people forget this.
The vast majority of programmers who started in the 80's and 90's are basically directly responsible for massive waves of job losses in certain categories. Lots of cases of entire departments of secretarial level paper-pushing work being replaced with a small team of programmers. Same will happen with AI tooling. The difference is programmers are no longer the "winning" party here.
Computers and software in the end are the most configurable and complex automation system society has ever created. They are simply a continuation of industrial automation, and AI is a continuation upon that.
It was never about software. That was just the means.
Even in the software era, fads developed and tech stacks changed frequently. Now it's just moving a hundred times faster.
You need smart systems thinkers to do this. That's the role. Be smart in managing processes and complexity.
I'm not going to give coding interviews anymore, but I am going to give architecture, systems design, and SRE interviews. People still need to know how not to fuck up a database and how to design scalable and resilient systems.