I work as a software engineer and a manager in a medical devices company, but also as a hobby, whenever I'm at the doctors, I always ask them to show me the sys

I work as a software engineer and a manager in a medical devices company, but also as a hobby, whenever I'm at the doctors, I always ask them to show me the systems they're using. A few observations: * software for medical devices is obscure, usually still done with 90s/00s technologies, people in the field are underpayed too. The result is you get bad code and most of the time you're just maintain it, instead of implementing new stuff, * this applies to both software and hardware - amount of often useless paperwork is ridiculous. You're bound by a lot of standards and regulations to make software/hardware compatible with those regulations. Which means engineering is not doing much engineering, but rather fillout those docs, do countless reviews of them, spend a lot of time on testing and QA. I know a few of those standards by heart, and often the work is not about implementing a standard but rather about being complaint with the standard - aka interpreting and stretching them that whatever you do is kinda complaint, but not really following the rules * software to manage these docs/requirements is also from 00s/90s, super not intuitive * med software itself, like stuff used by a doctor or folks in a hospital has really terrible user experience, sometimes it takes years to master it. Then once people master it, they get used to it, they don't like upgrades, cause then you have to master them again, * in my country you can do a lot of med stuff via email, what they call "encrypted email" - it's not PGP, and it's not encrypted with x509 certs etc You get like an email with a page embedded there that only works on Edge or Chrome, and to "unencrypt it" you need to put like data of birth or something like that. This market seems really miserable from software/firmware perspective. Happy to ask some more questions.