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
You would be amazed!
DDG since 2016 when I had to switch because I was in China. Never went back and with everything I hear about Google, I don’t plan to. Only Google thing I still have and enjoy is Maps.
Not one company I’ve worked at has ever paid a license for anything if it was at all possible to do it freely.
EPPlus trying to get money for their hard work? Guess we are stuck on the free version forever then…
It’s fucking embarrassing.
That’s what I did and I loved it. jQuery, some jQuery API, some dataTables, my backend in C# and off I go! Not perfect, but really enjoyable. Also SCSS is wonderful and I’m never going back.
It’s “four screens side by side” display. Why not, I guess.
Thanks for correcting. Pleco confirmed the one I wrote, but this is the one I learnt and actually wanted to write!
China, at least. Lots of distinction between mother side and father side. Grandma can be 老老 laolao (mother’s mother) or 奶奶 nainai (father’s mother), for example.
That has to be because in Chinese there is a single word for it, like for so many other relative nouns.
… I think I found it : 老表 (laobiao) Defined as “male cousin (on the maternal side or on the paternal aunt’s side)”
I’m embarrassed to say I only finally got it now. After reading the joke last night. -_-;
Backdoors all the way down!
A few months back I crashed a db in prod. I detached it and when I tried to reattach it simply refused, saying it was corrupted or some shit.
Lucky me we have a backup solution.
Unfortunately it was being upgraded, with difficulties.
That was a long day.
I worked for a big Euro bank for a bit and that was exactly it. JS timeouts were forbidden, so no animation to tell you something was finished, you had to keep clicking a Refresh button to know. In 2022.
And the colleagues who had been there a few years were actually defending this shit. Stockholm Syndrome is what it is. There wasn’t a day I didn’t complain about their piece of garbage of an intranet.
I’m so glad it’s behind me.
It is the way!
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.