The future is hardware engineers and predictive text chatbots:
I suspect it will actually be "system integrators" (a fancier title
than they deserve) with most of the hardware and software people
in very few locations (likely overseas).
Look at how many people slap together products from off-the-shelf
boards and prepackagd software. This, of course, leads to overly
complex products where the hardware and software people look
at the resources they now have (which typically exceed their needs)
and try to find uses for them.
"Oh, we can use the filesystem to store configuration settings as
files (instead of just bit fields in fixed locations in memory or
FLASH). And, can use shared memory as a fast form of IPC (because
the process contasiners you've inherited are too heavyweight).
And, the print spooler to support an external printer (that wasn't
'needed' in the initial design specification -- whatever half sheet
of paper that consumed!). And..."
Likewise, an examination of the hardware reveals overprovisioning
that tempts people to *add* complexity: "We can use the display to indicate..."
All of these mechanisms that weren't strictly NECESSARY (per the
original specification) suddenly are requirements. More stuff that
the "integrator" has no idea of in terms of its quality, vulnerabilities, maintenance issues, etc.
HR at white collar/cubical farm/SaS-type companies can just give up hiring for
a position and close it in despair when they get swamped with resumes, and just
spend what they'd have spent on salaries on more chat bots. But hardware companies probably eventually notice that hardware isn't getting designed.
People's Computer Module Factory #247B is there for all their needs.
Open source kernel/OS package 3506 brings it to life.
MTS are just needed to configure "setup screens"!
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)