You can use backreferences 1 2 etc. but you can also give them names explicitly.
it looks like this: (?<name>inner-regex)
Some flavors support it, kotlins doesn’t apparently.
Because this repo is going viral from time to time to developers, I’m open for discussion if you want to promote a product/service in this README file. Just mail me at XXXX
Named groups are nice but can I please define a group more than once because maybe I want to group my data and consolidate values in a logical way without you complaining I have already used a group previously. I know I did, I’m the one telling you, now capture it twice!
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
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.
IT workers desperately need to unionize. There is so much bullshit that happens, folks are expected to do three different roles at once, have multiple technical stacks they are experts in, and work extra hours + be on call after hours or on weekends.
100%. A full on IT Workers Union would immediately become one of the most powerful weapons in fighting the oppression of the capitalist class. An IT strike could be effective enough that a general strike wouldn’t be necessary
It can be. I often find it “bursty.” I’ve had months at a time when I had stand-ups and then “do whatever you want” for the rest of the day. I generally did do useful work, but there were plently of days when I was just chilling out.
Ive also had months where I ran from fire to fire while on fire, spreading even more fire. Also, there was fire.
It juat depends. If some org treats you as disposable, pays like shit and lights your hair on fire as you walk in, y’all should walk back out. The next org will probally treat you better, because there are good orgs out there. Even the good places get busy for a bit though. Just make sure that busy comes with money and that it ends at some point.
This is how I would describe my experience. Sometimes it’s crunch time and most of the time it’s fuck around time. After crunch time I always throw a tantrum about how if we only bothered with planning we could largely avoid it.
programmerhumor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.