More than 200 people with diabetes have been injured when their insulin pumps shut down unexpectedly due to a problem with a connected mobile app, the US Food and Drug Administration said Wednesday.

  • best_username_ever@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    2 months ago

    That’s what I thought before but it doesn’t matter. In medical devices you need good programmers and there are a fuckton of rules and tests to make sure that devices are safe. It’s also very regulated and usually well planned.

    Medical companies are the best for this because we’re all accountable directly or indirectly and we do our best. I know I would not work for another kind of coding job because they would all feel too random.

    I know mistakes can happen, but it’s the best environment you can work in if you’re a developer. Also you learn a lot and are surrounded with good devs who will make you better.

    Anyway, I’m not trying to convince you but we need people who doubt and could be careful. It’s not at every job but usually it’s: planning is good, overtime is not acceptable because it shows bad planning, tests are everywhere (all kinds of tests), merge requests are serious business (your merge request can sit for weeks before being integrated), doc is central and you have to be a part of it, etc.

    Last but not least you can still find the PDF of the IEC 62304 which shows every step that should be made to write medical software, and it could make you a better developer even if you’re not working in that field.