• 40 Posts
  • 2.05K Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle





  • Ephera@lemmy.mltoScience Memes@mander.xyzReal talk
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    3 days ago

    I don’t feel like these positions are at odds with one another, unless you become active in reducing the number of humans, of course.

    Like, you can uplift and protect people by stopping them from killing their environment, because you recognize that people are an invasive species that will do that.


  • If you’ve got access to a microwave, I’ve found rice dishes quite convenient, like for example a lentil curry. They generally re-heat without tasting worse and the rice traps the moisture, so even if your container isn’t 100% sealed, you’re unlikely to get mess everywhere.

    (Though I’d still recommend getting a properly sealed container. Personally, I also transport my food in a separate cloth bag, so that if it should ever leak, I can just wash that bag.)


  • Yeah, I always plead for as much as possible to be automated offline. Ideally, I’d like the CI/CD job to trigger just one command, which is what you’d trigger offline as well.

    In practice, that doesn’t always work out. Because the runners aren’t insanely beefy, you need to split up your tasks into multiple jobs, so that they can be put onto multiple runners.
    And that means you need to trigger multiple partial commands and need additional logic in the CI/CD to download any previous artifacts and upload the results.
    It also means you can restart intermediate jobs.

    But yeah, I do often wonder whether that’s really worth the added complexity…


  • I always thought openSUSE’s package manager zypper has quite a few neat ideas:

    • It offers two-letter shorthands for subcommands, so zypper installzypper in, updateup, removerm.
    • When it lists what packages it will install or remove, it will list them with the first letter highlighted in a different color, kind of like so: fish git texlive
      This makes it really easy to visually scan the package list, and since it’s sorted alphabetically, it also makes it easier to find a particular package you might be looking for.
      And while there’s separate lists for packages to be added vs. updated vs. removed, they also color those letters in green vs. yellow vs. red, so you can immediately see what’s what.
    • When it lists items (other than packages), it prints an ID number, too.
      So, zypper repos gives you a list of your repositories, numberered 1, 2, 3 etc., and then if you want to remove a repo, you can run zypper removerepo 3.
    • When you run a zypper search, it prints the results in a nicely formatted table.

    Documentation: https://doc.opensuse.org/documentation/tumbleweed/zypper/



  • What I find tricky, is that you’re always describing a work-in-progress. I also wanted it to be useful as soon as possible, so I started building the actual core logic first and documented that part of it.

    But to actually use it, you need several steps before, which need to be documented, but preferably automated or ideally eliminated.
    So, you kind of don’t want to invest time documenting that, because you know it’ll change a lot still.

    And just as well, any quirks you document, it’s always like, okay, but what if I fixed this quirk instead?

    Obviously, one has to strike some kind of balance. Things will never be 100% perfect or final. And I am most definitely lying to myself, when I figure that fixing it won’t take much longer than documenting it. But yeah, it’s just a constant struggle to find that balance…






  • Yeah, this is one of those issues that I feel separates the seniors from the, uh, less experienced seniors. (Let’s be real, as a junior, you know jackshit about this.)

    Knowing when to use an ORM, when to use SQL vs. NoSQL, all of that is stuff you basically only learn through experience. And experience means building multiple larger applications with different database technologies, bringing them into production and seeing them evolve over time.

    It takes multiple years to do that for one application, so you need a decade or more experience to be able to have somewhat of an opinion.
    And of course, it is all too easy to never explore outside of your pond, to always have similar problems to solve, where an SQL database does the job well enough, so a decade of experience is not a guarantee of anything either…




  • I do agree, yeah, although I can certainly also understand LISP fans being annoyed that someone created a custom DSL for something that is adequately solved by the LISPs. I’m also certainly not enamored with the Nix syntax myself, but do find it easier to parse than a million parentheses.

    But yeah, ultimately the complexity of Nix and Guix isn’t in the particular symbols you type out. The complexity comes from them being expression-based (which does make sense for the use-case, but isn’t as familiar as e.g. imperative languages), as well as just having to learn tons of modules for the different things you want to configure…


  • Wikipedia seems to do a decent enough job defining it:

    Authoritarianism is a political system characterized by the rejection of political plurality, the use of strong central power to preserve the political status quo, and reductions in democracy, separation of powers, civil liberties, and the rule of law.

    But basically, my point is:

    • If your government represents the people, then it is possible for your people to elect authoritarianism, especially if they are unhappy, like the meme describes, and/or when there’s foreign nations trying to destabilize the system.
    • If your government does not represent the people, then it is likely to devolve into authoritarianism on its own, because individuals or individual groups will want to assume all power and limit the rights of others.

    Basically, my opinion is that politics is a constant work in progress, no matter the political system.