• 20 Posts
  • 935 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • There’s a small mountain just 200 meters from my home. Tried to go up there once, but realized halfway that you need proper shoes for that. It’s in the middle of town, but still unsecured wilderness, so you feel like you’re climbing a proper mountain pretty quickly. Basically, the kind of experience that others will drive out into the countryside for.

    And the thing is, I do have proper shoes at home. I’ve been meaning to head back up there and to the top, to get the proper outlook (which has got to be pretty fucking cool, since you can see the whole town even from halfway up).
    But yeah, because I could head up there at any point in time, it’s always been a matter of “Oh, it’s too wet this weekend” or too icy or too hot or any other excuse.
    Like, yeah, maybe don’t climb a mountain when it’s icy, but none of the other reasons would’ve stopped me, if I was here on vacation…




  • Yeah, management wants us to use AI at $DAYJOB and one of the strategies we’ve considered for lessening its negative impact on productivity, is to always put generated code into an entirely separate commit.

    Because it will guess design decisions at random while generating, and you want to know afterwards whether a design decision was made by the randomizer or by something with intelligence. Much like you want to know whether a design decision was made by the senior (then you should think twice about overriding this decision) or by the intern that knows none of the project context.

    We haven’t actually started doing these separate commits, because it’s cumbersome in other ways, but yeah, deliberately obfuscating whether the randomizer was involved, that robs you of that information even more.


  • Yeah, that’s my biggest worry. I always have to hold colleagues to the basics of programming standards as soon as they start using AI for a task, since it is easier to generate a second implementation of something we already have in the codebase, rather than extending the existing implementation.

    But that was pretty much always true. We still did not slap another implementation onto the side, because it’s horrible for maintenance, as you now need to always adjust two (or more) implementations when requirements change.
    And it’s horrible for debugging problems, because parts of the codebase will then behave subtly different from other parts. This also means usability is worse, as users expect consistency.

    And the worst part is that they don’t even have an answer to those concerns. They know that it’s going to bite us into the ass in the near future. They’re on a sugar high, because adding features is quick, while looking away from the codebase getting incredibly fat just as quickly.

    And when it comes to actually maintaining that generated code, they’ll be the hardest to motivate, because that isn’t as fun as just slapping a feature onto the side, nor do they feel responsible for the code, because they don’t know any better how it actually works. Nevermind that they’re also less sharp in general, because they’ve outsourced thinking.


  • Today, I noticed that my glasses case sticks to my work laptop like a magnet.
    I played around with it for a few seconds, then the thought struck me, that it might be my glasses case that’s magnetic, and I might be fucking up the electronics or the HDD or something by holding it close to my laptop. Pulled away real quick then. 😅

    I did try with my keys later, and well, turns out that it’s my work laptop that’s magnetic, so I guess, I wasn’t fucking anything up after all…



  • Arch basically happens at a granularity of individual packages. You decide from the ground up which packages you actually need, which is how you end up with a comparatively minimal setup.

    But yeah, if the package itself is big, then Arch doesn’t usually deal with that. The Linux kernel comes with drivers for most hardware out of the box, which you can remove, if you know you won’t need that hardware.
    And while this can also be done on Arch, it is Gentoo’s thing to do precisely that.




  • I imagine, it has also manifested in our culture for women to exert an abundance of caution and to try to gauge reactions as long as possible, because playing it entirely open can lead to the man developing feelings, and if you then have to break things off, it can get ugly. Some men, even if it is just a tiny fraction, may then turn to violence and rape.

    In particular, the men may “blame” you for their feelings and they might feel “”“justified”“” in raping you, because you did tell them that you find them attractive. No, none of this makes sense and I’d need to order another bucket of quotation marks, if I wanted to try to continue making sense of it, which I don’t, so let’s not do that.


    Yes, the same can happen with the genders reversed, but typically the men are physically stronger, which is why this power dynamic made it into our culture, at least according to my pet theory here.