• 1 Post
  • 460 Comments
Joined 10 months ago
cake
Cake day: November 13th, 2023

help-circle
  • I was in the “gifted/advanced” track too. Teachers saw this one of two ways. Half of them got the memo: you got extra interesting stuff to noodle through because we’re all under-stimulated in a typical class. The others decided to just double your homework load and call it a day. At least the teachers in the first group had some interesting takes on brain teasers and reading material.

    And on that note: I must have thought about Flowers for Algernon every week since I read it. Since the 90’s. I’m tired, boss.


  • Sometimes teachers field stories like this to foster critical thought and encourage insightful book reports. It’s stimulating material even with a flawed premise, and that’s the point.

    My teachers always seemed to be the type that had these stories in the curriculum, but weren’t the type to follow up with the thinky-thinky bits. This had rather predictable results.




  • Put any distro in front of me and provided I don’t need to master it, I’m good. Ubuntu is fine. Debian is fine. RedHat is fine. Fedora is fine. I even have a tiny low-end system that is using Bohdi. Whatever. We’re all using mostly the same kernel anyway.

    90% of what I do is in a container anyway so it almost doesn’t matter; half the time that means Alpine, but not really. That includes both consuming products from upstream as well as software development. I also practically live in the terminal, so I couldn’t care less what GUI subsystem is in play, even while I’m using it.


  • The only time I’ve encountered people that care a little too much about what distro is being used, is right after having transitioned to Linux; the sheer liberating potential of the thing can make you lose your head.

    I’ve come across a lot of professional bias about Linux distros, but that’s usually due to real-world experience with tough or bad projects. Some times, decisions are made that make a given distro the villain or even the hero of the story. In the end, you’ll hear a lot of praise and hate, but context absolutely matters.

    There’s also the very natural tendency to seek external validation for your actions/decisions. But some people just can’t self-actualize in a way that’s healthy. Sprinkle a little personal insecurity into the mix and presto: “someone is getting on great with that other Linux I don’t use, so Imma get big mad.”








  • and for what!?

    Ultimately? For humble pie.

    The British were so hangry, so incredibly hung-over, so fed-up with the limited cuisine at home, that they colonized half the planet in search of a proper meal like their very lives depended on it. And for a time, the spice did indeed flow. But that quest cost countless lives, started many wars, and ultimately, ended in defeat. In the end, some people from those far off lands, now liberated, emigrated to their conqueror’s homeland of their own free will and brought their pantries with them. In so doing, perhaps with a spicy side of defiance, meals are served in London daily that provide a reminder of how the surrounding kingdom is a mere shadow of it’s former self.






  • Honestly, this is why I tell developers that work with/for me to build in logging, day one. Not only will you always have clarity in every environment, but you won’t run into cases where adding logging later makes races/deadlocks “go away mysteriously.” A lot of the time, attaching a debugger to stuff in production isn’t going to fly, so “printf debugging” like this is truly your best bet.

    To do this right, look into logging modules/libraries that support filtering, lazy evaluation, contexts, and JSON output for perfect SEIM compatibility (enterprise stuff like Splunk or ELK).