What Software Engineering domains require the least continuous learning?
In most domains where software engineering is involved, one has to continously learn, unlearn, relearn new languages/frameworks/technologies or what have you.
What domains require the least continuous learning?
If I had to answer my own question, I'd probably bet on safety critical software, but I'd like to hear what the community has to say :)
Hardware changes the slowest so advances that affect how chips, processors and boards tend to be more predictable and long-winded. However, the application of these changes to different domains (e.g. IoT) changes rapidly so the underlying hardware platform may be "stable" but new requirements that need to be programmed (e.g. power efficiency, security, etc) will continue to evolve -- therefore requiring continuous learning.
You could try lower level, like anything with microprocessors, industrial robots, data communications, or healthcare. The kind of things that use C or Assembly. These will still be in high demand and highly paid as IOT/Industry 4.0 tries to catch on.
You could always dive into something ancient like COBOL that is objectively never going to change, but people will always need. Same goes for similar languages of that era (FORTRAN, etc.)
More learning is necessary in areas which are more prone to changes.
Hardware architecture and hardware itself are the least changing parts related to software engineering. And as the result OS kernel level development and system programming don't require to relearn that often.
Companies started in the last 10-15 years that started and ended on a mostly Java-based stack.
The business should also be super stable, slow growth, but high revenue/margins. That's probably the most important thing you should look for.
Big tech companies, cable companies, banks, FAANG, utilities, etc.
Just stay away from agencies and startups.
Enterprise .Net shops. 90% of their work is CRUD, but you aren’t stuck as unemployable. Low innovation, 8x5, pay can be very good.
Any legacy system - but your skillset then becomes tied to domain knowledge. This can be both good and bad - the good is your valued as long as the system exists, the bad is once the system is replaced you can be on a rocky path
I would challenge the idea that you must continuously learn. It's entirely possible to have become a Java/Spring specialist and continue to remain employed into 2020 and likely well beyond.
The churn you're alluding to happens mostly at the very thin frontier of innovation and applies largely to engineers who want to retain high compensation.
Continuous learning is a fundamental part of the job. Some of the answers here focus on stable tech stacks but in reality even if you spend your entire career using the same tools, you still need to be continuously learning new things within that stack just to keep up.
Cobol should probably be up there on your list.
Banks tend to be pretty risk averse and will maintain working code for as long as they can before adopting new technology.
Try something like C where changes come very rarely. Avoid going to Flutter or Dart!
front-end web development