I completely agree with the general assessment, but then there are always pesky exceptions. In this case the list entered a JavaScript frontend from the yaml header of machine generated content pages for the website framework Hugo. And, of course, after finding the bug, it is clear that things could have been done differently and the issue easily avoided, but I also don’t think this was a completely unreasonable design. Since Hugo actually supports JSON headers (not just via the yaml parser, but thanks for that tip!), that was a quick fix. But I’m also somewhat amazed that it was possible for the strung-together fairly standard set of Python libraries (primarily pyyaml) to not get the strings properly quoted.

Just the other day I had a list show up as [“a”, “b”, “c”, “d”, “e”, false, “g”, “h”, “i”].

The issue was that, without me being overly aware of it, the data was going through a data -> yaml -> data step.

Yes, the data -> yaml filter was broken for not putting general strings in quotes. But IMO the yaml design invites these odd “rare” bugs.

I used to like yaml, but was happy to see Toml taking the niche of human-readable-JSON, but felt the format for nested key-value was a weird choice. However, I’ve always felt we could just have extended JSON a bit (allow line breaks, comments, if the outermost data type is an object, the curly brackets may be omitted).

Even knowing the “correct answer” to this riddle for as along as I remember, I don’t think it is right. For someone looking for how to handle this in an interview, I’d go with this:

I will fetch a friend or colleague to look at the bulb as I test the switches because:

• It is by far the most obvious solution that literally everyone faced with this problem actually would use. It is easy to understand and will be easy to explain to others (if you, e.g. need to present or document what you did).

• It is also a better solution: it is by far more robust against a large number of failure modes: e.g., if it turns out you are testing the wrong switch, the bulb is broken, more than one switch turn on the light, etc.

• It scales better: the same solution trivially extends to N number of lightbulbs controlled by M number of switches; and at large N it will save time not having to reach each bulb.

• It gives the opportunity to interact positively with a friend/coworker. Helping each other out with small necessary tasks builds team cohesion and work environment, and thus lowers the barrier for further collaboration, making us a more effective team in the longer run.

What kind of nerds do you claim to be in this thread?! Despite being late, I see no mention of the xkcd color survey: https://blog.xkcd.com/2010/05/03/color-survey-results/

As far as I can read just by eye, its “mustard” or “olive”, but funnily it also seem close to the one someone annotated: “really? this color again? i have nothing against colors personally, but this one just stands out from the rest as unusually unattractive. i almost feel sad for it, but it made the decision to be that color so it has to find a way to deal with it.”

But, someone, feel free to dig into the hex codes to give a more definite answer.

I’m in this meme, and I don’t like it.

Are you using x11 or Wayland? Is anyone running Wayland with NVIDIA drivers? Everything works well in x11, but I’m getting bad flicker in Wayland. When trying to track it down I was led down a rabbit hole suggesting there is some protocol mismatch between what the NVIDIA drivers implement and what Wayland expects.

MasterCard’s and Valve’s statements seems to point at Stripe and PayPal as the ones who folded to the pressure. These payment processors then cited MasterCard’s rules to back up their change in policy.

MasterCard now clarifying that the payment processors are over-interpreting the rules and anything legal is ok seems a very good thing here. Valve should be able to go back to Stripe and PayPal with this and say: “Hey, you’ve misunderstood the rules you are quoting; MasterCard themselves say anything legal is ok, and that is the exact policy we’ve been using!”

Also id probably lose 4 of these before giving up outright.

You buy them in bags of 20ish, and keep buying them until you have established an equilibrium in your home where there always are a few around to put on new bags. I’m not joking.

These two are not interchangeable or really even comparable though?

For GNU Make, yes they are. These are fully comparable tools for writing sophisticated dynamic build systems. “Plain make”, not so much.

[cmake] makes your build system much, much more robust, far easier to maintain, much more likely to work on other systems than your own, and far easier to integrate with other dependent projects.

This is absolutely incorrect. I assume (although I have never witnessed it) that a true master of cmake could use it to create a robust, maintainable, transferable build system. Very much like there are people who are able to make delicate ice sculptures using a chainsaw. But in no way does these properties follow from the choice of cmake as a build system (as insinuated in your post), rather, the word we are looking for here is: despite using cmake.

I apologize for my inflammatory language. I may just have a bit of PTSD from having to build a lot of other people’s software through multiple layers of meta build systems. And cmake comes back, time and time again, as introducing loads of obstacles.

Cmake

ADA should be the lawful good.

Bash is chaotic neutral.

Java is lawful neutral.

Javascript fits ok as chaotic evil.

Move ASM to neutral evil.

And maybe f77 as lawful evil.

I made this the other day.

Anyone want to team up to build a time machine and travel the future until the perfect utopia is achieved?

How about we team up and try to make this world better instead?

Nope, this redefinition isn’t necessary, it is a choice SI made. Nothing would have broken by keeping an exact relationship between amount of substance and mass, it would just have retained the interpretation of Avogadro’s constant from before 2019 (experimentally determined vs a defined constant).

… weighs one gram … An amount of hydrogen weighing the same amount has exactly one mole of atoms in it.

Not only was this never true - the sentence would have to have say “An amount of carbon-12 atoms weighing 12 times this amount has exactly 1 mole atoms in it” (far less elegant) – but not even this is true any longer after the fuckup in redefining the mole in 2019, after which all these relations between amount of substance and mass are only approximate.

This whole rapey lingo needs to fucking die already.

Maybe widely name-calling this practice for what it is could help steer companies away from this disgusting pattern.

Should we start refering to pop-ups that give no option to say “no” as something like “rape-ups”?

After checking that you can open port 53 udp yourself with, say, nc (which you tried), strace the binary that tries to open port 53 and fails, and find the system call that fails. You can compare it with an strace on nc to see how it differs.

If this doesn’t clue you in (e.g., you see two attempts to listen to the same port…) Next step would be to find in the source code where it fails (look for the error message printout) and start adding diagnostic printouts before the failing system call and compile and run your edited version.

Better yet, demand loudly to get a refund. When they say there is nothing to refund, insist that you have an email confirming a booking.

Here is a DallE rendering of the same setup that maybe is less offensive.

https://youtu.be/jI2zxBAIepI