An idea that I have thought of is to standardize on some programming language/frameworks/demands that are known to be supported for a very long time (15 years?). If you need something from this buffet, you are fine and have the advantages that this provides. If you have special demands, you are on you own - which is not a problem per se, but as all special demands this simply needs to increased risk or cost.
I'm exhausted and frustrated with the field as it exists just now.
We've had about 60 years to figure this stuff out, and arguably the ground is always moving beneath our feat as the nature and scope of the systems we build keeps changing.
I'm exhausted and frustrated with the field as it exists just now.
Likewise, but I'm not sure what choice we have, except to hope Ray Kurzweil is right about some of this life extension ideas. If we can survive another 300-400 years, maybe things will be better.
How could you do that for software engineers? There are so many programming languages, frameworks out there that are constantly evolving and companies have different demands.
I think it would be a really hard problem to generalise.