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

help-circle
  • The thing to me is always that, yeah, you need a huge commit for a breaking change in an internal library inside a monorepo, but you will still need to do the same work in a polyrepo eventually, too.

    Especially since “eventually” really means “ASAP” here. Without going through the breaking change, you can’t benefit from non-breaking changes either and the complexity of your codebase increases the longer you defer the upgrade, because different parts of your application have different behavior then. So, even in a polyrepo, you ideally upgrade all library consumers right away, like you’re forced to in a monorepo.


  • Good question. My best guess is that the buttons have become less important, because:

    • they try to auto-detect where a signal comes,
    • they have better defaults, so you don’t really need to change settings, and
    • even monitor brightness can partially be controlled by the OS.

    But yeah, I got a new monitor at work, and instead of buttons, it has a joystick on the backside. Now the monitor’s menu pops up every so often, I’m guessing because something shook the joystick just enough to trigger it.
    When I saw that joystick for the first time, I wondered how long it’ll take before it breaks, but it’s broken on day 1, so that’s great. 🫠


  • Ephera@lemmy.mltoScience Memes@mander.xyzPeas plz
    link
    fedilink
    English
    arrow-up
    6
    ·
    24 hours ago

    I believe, the problem is mainly white bread, which is what people typically have in mind for feeding ducks.

    As opposed to wholegrain, it only retains the endosperm, which is mostly just carbohydrates without many nutrients:

    I think, the lack of fiber is also particularly problematic. At least, I’ve heard that it gives them diarrhea, which probably means their guts don’t have time to extract the few remaining nutrients.







  • A few years ago, I set up a home-server with music and some pictures on there, and recently I noticed that my storage disk was getting full. Then I saw that the disk only had 16 GB and wondered, where the hell I got that small of a disk from.

    So, I go to plug in a bigger disk and can’t even find the original disk at first. Turns out my whole storage capacity was one of these bad boys:

    Spoiler

    A tiny USB-A stick, designed for keeping it plugged into a laptop at all times.

    And yeah, I’ve got about 1800 songs, clocking in at 5.8 GB, so even that tiny storage would easily be enough for a much larger collection.
    And I do also have them replicated on my phone, for listening on the go. (Don’t even need an SD card in my case.)




  • I’m weirdly deeply invested, like I’ve got decent headphones, I’ve composed songs before, I’ve played two instruments, and like someone else posted, I’ve also implemented my own music player program.

    But man, I struggle with feeling it as art. I don’t know, if that’s a case of music-maker being snobby about everyone else’s music, while being too critical of their own music. Maybe my expectations are just too high.
    Like, I’m trying to create lyric-less music where I feel a meaning. And at times, I’m amazed that I can evoke the sense of snowfall. But at many other times, it just sounds paperthin to me, and I still haven’t managed to really portray a deeper meaning.

    Maybe I’m just frustrated, because poems come more naturally to me (and yes, I am dense for not adding lyrics to my songs 🫠).




  • Their primary purpose certainly isn’t the same, but with JavaScript being used to implement text editors, it’s in a playing field where many would argue that Rust is better suited.

    Well, and Rust can play in JavaScript’s playing field, too: You can implement webpages in HTML+CSS+Rust by going through WebAssembly.


  • Man, at $DAYJOB, if we open-source something, they tell us to check for checked-in passwords and whatnot, and force us to throw away the commit history, which always feels stupid when we’ve known upfront that we’re going to open-source it and so kept things clean from the start.

    But then, yeah, you see a post like that and just think that it really wouldn’t have been too difficult to search for swear words before publishing.
    I mean, I also don’t really care, since it’s code rather than an official communication channel, but I can understand why management might care.


  • Man, I keep having that problem, that some car or motorcycle sounds like it needs a repair to me, only for me to realize that, no-no, they want it to sound like that.

    Just yesterday evening, I heard someone revving before accelerating again after a stop at a crossing, and if they would’ve gotten out of their car at that point, I might’ve shouted over that, damn, sounds like they need to get their clutch looked at.
    Genuinely thought they failed to engage a gear multiple times. Meanwhile, they would’ve probably punched my face in, if I insulted their car like that. 🙃


  • I mean, modern package managers generally now come with lock files, which effectively auto-pin your dependencies, until you trigger a dependency update.

    And while it isn’t bullet-proof, it does result in you effectively having a dependency cooldown most of the time. You’re only vulnerable, if you trigger the dependency update while the compromised dependency release is public.

    Obviously, this can be bad enough, but it does also mean that an ecosystem with lock files is far less attractive to target with a supply-chain attack, since far fewer hosts will get compromised on average.



  • One time, I had to request firewall access for a machine we were deploying to, and they had an Excel sheet to fill in your request. Not great, I figured, but whatever.

    Then I asked who to send the Excel file to and they told me to open a pull request against a Git repo.
    And then, with full pride, the guy tells me that they have an Ansible script, which reads the Excel files during deployment and rolls out the firewall rules as specified.

    In effect, this meant:

    1. Of course, I had specified the values in the wrong format. It was just plaintext fields in that Excel, with no hint as to how to format them.
    2. We did have to go back and forth a few times, because their deployment would fail from the wrong format.
    3. Every time I changed something, they had to check that I’m not giving myself overly broad access. And because it’s an Excel, they can’t really look at the diff. Every time, they have to open it and then maybe use the Excel version history to know what changed? I have no idea how they actually made that workable.

    Yeah, the whole time I was thinking, please just let me edit an Ansible inventory file instead. I get that they have non-technical users, but believe it or not, it does not actually make it simpler, if you expose the same technical fields in a spreadsheet and then still use a pull request workflow and everything…