>>105895197 (OP)EEs have become so fucking autistic that basically none of them really know how to use git, or any scm for that matter, know how to write simple bash scripts to automate anything, or really do much except shit out shitty C that they don't know either. They are completely unprepared for the world where everything has its own buggy firmware, complex caching hierarchies (sprinkle volatile until it works, if it never works -O0, if that doesn't work cannabalize another driver, repeat, wow muh gpio werks now), and just basic shit like how to install Linux, how to adjust filesystem permissions, how to build programs from source, literally just basic shit.
Those are "successful" people. When they get a dump of platform code from $vendor, they can't even get it into git and then understand you probably need an old Ubuntu plus build-essential, and that you can try shit in a VM, and once it works you can probably even rip a chroot and run it on whatever, because build autism doesn't generally care about differences in kernel, etc, etc, etc.
Basically what we have is CS retards are Indian react shitters who can AI street shit python, and EEs who may be experts in antennas or power distribution but unable to issue basic commands over i2c or spi or whatever and simply export this to userspace for street shitters to interface with, it's a fucking mess. And good luck finding anyone who has ever rebuilt theirown kernel or bootstrapped gcc or installed gentoo O3 or Os for their arch, etc. Or who may understand what a restrict pointer is.
So, what the industry is looking for are young people who are really just oldfags that may be able to tardwrangle oldfags-in-name-only EEs into getting normal software processes in place, just basic shit like branching, releasing (for internal use), release noting, versioning, using JIRA, having a Confluence page, etc. Jesus fuck, it's like an intervention episode when EEs have a simple merge conflict.