Lots of bold, unsubstantiated claims. I think every time there is a big peak, or a big valley, some percentage of people are always peddling "but this is different"
I'll never understand this sentiment. You don't have to have alerts from slack outside of business hours. Or respond in general. If I responded or looked at my messages every time I got one, I'd never get work done... so I simply ignore them until I am taking a break or otherwise at a good stopping point. It's not that hard.
You gave yourself away as ignorant when you tried to explain that the system is optimized for doctors.
This is especially rich on a forum like hacker news, where we have many software developers who went to school for ~4-6 years and fairly regularly make as much as the doctors who round the hospitals, who also kept incurring debt and made basically no money until they were 30.
This seems like there isn't buy-in to the OKRs across your employer. My company does OKRs and it's taken seriously by VPs as well as the devs. Here, it's very reasonable to say no to something (and have that be respected) because it's not contributing to your team's OKRs. If it's a VP or something and insists it needs to be done then that means the OKRs need to be updated to reflect the nature of this work.
I think I agree with you - I'm just trying to understand the other perspective from someone that seems to think not having exceptions is an improvement. I've mostly worked using java and go and to be honest I think I prefer exceptions because you should (almost) always check error codes in go anyway, and if you forget, you just made debugging much more difficult.
Aren't you supposed to check all the possible errors in golang anyway? How's that any different than java code being littered with error handling code?