Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FI
Posts
0
Comments
759
Joined
2 yr. ago

  • Yeeep. We are on the same wavelength. I literally opened my argument with the same idea, last time we had the convo : she's the one with the doctorates, plural. She should be the one telling them what she can and can't handle. Feck, her head doctor is on the same page too. Unfortunately that sort of power seems to come with age and even at 40 she still doesn't have that kind of attitude. One could attribute this to her gender, I suppose, but having seen my dad do exactly the same thing throughout his career until he reached near retirement age, and having seen all my dad's colleagues do the same thing, hopefully you get the idea.

    There just isn't enough time and too many patients for not enough doctors. Always. And most doctors want to help their patients, so they just don't count the hours, until the work is done.

  • Unfortunately the doctors usually aren't the ones managing the schedule. The admin / secretaries are.
    And good ones, that understand that a new patient with no file, that doesn't speak the language, that has a history of complications with her previous pregnancies, etc is not gonna be a normal half hour consultation are extremely rare.
    Even kind ones that see that you are swamped day in day out just seem to assume that these are teething difficulties, adapting to the position, etc (even after almost two years).

    And so that's how my wife ends up doing a ten hour workday. Nonstop. With no break for lunch because hey, too bad, she finished the morning shift two hours late and now her first afternoon appointment has been waiting for half an hour...

    But of course if you tell patients there is no time for them because the few doctors that are here are already overworked...

    (to be clear, I've been saying the same thing as you to my wife for two years now. But apparently the message is not getting across)

  • Indeed. It was thirty years ago but I vividly remember the intersection and seeing the lights from my right and being like "well, fuck me! What's this asshole doing on the road at this hour?"

  • And the classic "it's 3am, on a countryside backroad intersection. Surely nobody..."
    But yesbody! There it is, a car coming at full speed, exactly at the moment I'm about to engage on what should otherwise be an empty road.

  • JsonSchema is a way to validate some JSON. A great thing when you want to stop any sort of malformed data from coming in. Instead of wrecking your head in your code testing whether this bit here is not null, or is that string a valid boolean (I still remember that shitty piece of code they had, ugh!) or that bit is empty or that one is an actual number, or a string that can only have such and such value, well, you can formalise all this in one place, as a data file instead of code. Very convenient.

    Except when it turns out you're using a JSON library that's not one, not two, but six major versions behind, and the security department won't greenlight you using anything recent because... fuck you, that's why. And to add insult to injury, we were the Quality department. Responsible for analysing the code quality of thousands of coders, around a hundred thousand programs (mostly COBOL but also C#), of a European banking group... The JSON schema was for adding a layer of non existant security to our API. But no, let's keep accepting shitty malformed JSON (because of course we kept receiving shitty JSON; that's why we wanted to implement this)

    So I had to rewrite a lot of custom code to patch the bugs we found in the library, and none of the nifty tools that let you put in json and generate json schema would work for us. Heck, they even have JsonSchema to validate your JsonSchema but those wouldn't work either, so far behind our version was.

    Fucking awesome experience. I'm glad it's behind me.

  • I wouldn't* be surprised if she didn't drive. My wife has no conception of how difficult even just picking up someone can be, and demonstrate it time and again, standing on the other side of the road, or at a corner where I'll block all trafic if I stop.

    Finding a sweet spot right in front of the place we wanna go would be like "well, yeah, you don't expect me to walk, do you?" for her, while I'd probably be as ecstatic as that poor guy.

  • I feel this in my bones. As an OG dev, I had this incredible urge to smack people when I was working for my last job and I saw the API specs with everything being sent as strings through JSON. Boolean? Sure, let's use a string. Integers? Sure we'll do conversion in our code, that'll be more efficient... So fucking infuriating. Oh and don't get me started on JsonSchema T_T

  • Happened a few times in China "hey this is your delivery man. Sorry, I clicked the button to reach my quota but I'm still on my way. I'll be here in a few minutes though, don't freak out ok?" Never would dream of complaining, they are so good.