Remember when Darl showed some “encrypted code” that he claimed was stolen and added to Linux and it was really just some POSIX definitions from a header file taken from BSD “encrypted” with a wing dings font? Those were some wild times.

Sisters Euclid. They were a Canadian band who recently called it a career after like 27 years of mostly-under-the-radar instrumental jangle jazz, or something to that effect. They did win a Juno for an album of Neil Young instrumentals and reinterpretations called “Run Neil Run”, but outside of the Toronto are and southwest Ontario I don’t think they were widely known. Members of the band have played in all sorts of other bands and with other folks, many of which y’all would recognize like Norah Jones and the Doobie Brothers, they all really accomplished musicians. I saw them live dozens of times before they called it a day, and I always saw and heard something new with every performance. Seeing them live was definitely the best way to take them in, as their studio albums seemed like they were just scaffolding for the live shows.

Hoping for a reunion show in 5-10 years. I’d travel for it.

https://sisterseuclid.bandcamp.com/

I haven’t posted on Reddit since they treated third party app devs like shit. I’m done with that site.

Ligature, not lineature.

“What one programmer can do in one month, two programmers can do in two months.”

Exit codes from processes are damage points that you take against your HP. When your HP runs out, the distro reformats itself to a clean state.

Don’t forget the interactive video they did for an anniversary thing a few years back.

http://video.bobdylan.com/

I wouldn’t say quite the same root cause — the xz back door was clearly intentional, but I don’t recall the Heartbleed bug having been intentional, and developer responsible has denied allegations to that effect. There can be no doubt in the xz case of malicious intent.

Code, editors, terminal, and most browser tabs on the right…

Calendar, Slack, some more browser windows on the left, sometimes some debugging tools.

Third smaller screen off to the side for media if I want to throw on something in the background.

That’s easy, just create new accounts every time you login.

Streetlamp Le Moose

There are 10 kinds of people in the world — those who understand binary and those who don’t.

The performance improvements in v4 are for compilation times, not rendering.

Learn to use git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.

Why wouldn’t you just create a GUI interface in Visual Basic to track their IP addresses tho?

Maybe we’re already there and death is just the garbage collector freeing up more space.

Many password managers like 1Password and Last Pass and KeePass and all the big ones can store MFA details nowadays.

The code in the image is C or C++ or similar. In those languages and languages derived from them, curly braces are optional but the parentheses are required. It should be the other way around to avoid logic errors like this:

if (some expression)
  doSomething()
else if (some other expression)
  printf(“some debugging code that’s only here temporarily”);
  doSomethingElse();

Based on the indentation you’d think that doSomethingElse was only meant to run if the else if condition was true, but because of the lack of braces and the printf it actually happens regardless of either of the if conditions. This can sometimes lead to logic errors and it doesn’t hold up to a principle of durability under edit — that is, inserting some code into the if statement changes the outcome entirely because it changes the code path entirely, so the code is in a sense fragile to edits. If the curly braces were required instead of optional, this wouldn’t happen.

I have all of my linters set up to flag a lack of curly braces in these languages as an error because of this. It’s a topic that sometimes causes some debate, ‘cause some people will vociferously defend their right to not have the braces there for one liners and more compact code, but I have found that in general having them be required consistently has led to fewer issues than having arguments about their absence, but to each their own. I know many big projects that have the opposite stance or have other guidelines, but I just make ‘em required on my own projects or projects that I’m in charge of and be done with it.

I also sometimes wish that the syntax in if statements was inverted, where () was optional and {} was required.