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.
Same in the medical devices industry. We have whole teams of non-developers whose job is to find out when and why a surgeon can be a moron. The code is more difficult to write, but it's way better and more robust.
In one of those weird return None combination. Also I don’t get why it insists on using try catch all the time. Last but not least, it should have been one script only with sub commands using argparse, that way you could refactor most of the code.
Also weird license, overly complicated code, not handling HTTPS properly, passwords in ENV variables, not handling errors, a strange retry mechanism (copy pasted I guess).
It’s like a bad hack written in a hurry, or something a junior would write. Something that should never be used in production. My other gripe is that OP didn’t learn anything and wasted his time. Next time he’ll do that again and won’t improve. It’s good if he’s doing that alone, but in a company I would have to fix all this and it’s really annoying.
You say it's magical but never post proof. That's all I need to think it's shit. No need to debate about it for hours. Come back when you entice us with something instead of the billion REST APIs that are useless but seem to give a hard on to all the AI bros out there.