• by eplanit on 8/23/2021, 1:32:25 AM

    You should try embedded systems work, Board Support Package (BSP) development, in particular. BSP development is about adapting an OS to a particular (usually new) board design/implementation. You have to understand how the system works from a bare-metal perspective, and most everything is problem-solving. The guiding motivation is what I came to call FIO "Figure It Out" -- often with little and/or poorly written documentation. It'll get you deep into the kernel (of whatever OS), device drivers, chip specifications (architectures, register configurations, modes of operation, ...), SoC's, microcontrollers, ... It's a fascinating, though low-level, world.

    I advise this sincerely, as I did it for 10 years, and enjoyed it a lot. However, I got myself back "above ground" and into systems and apps again, because my inclination is actually exactly the opposite of yours: "I could care less about “making” things; all I care about is “fixing” things".

    Over time, although the gratification of getting things to work remained, I grew tired of FIO every. single. day. I longed to again design and create solutions -- to "make" things. Different strokes for different folks. Best of luck to you.

  • by rdtwo on 8/24/2021, 12:43:49 AM

    QA is a bad role. I’d never recommend it to anyone. You are always the messenger that gets shot and you get fired for both being too good, too bad at your job and being unlucky. Never let friends go into qa.

  • by 2rsf on 8/23/2021, 12:26:58 PM

    Usually QA is used to describe test positions, is that what you are aiming for?