I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 2 Posts
  • 167 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle






  • The only task of a DNS server is (or should be) to tell you how to get to a resource you’re looking for by name. So, the only thing that is going to be reallistically affected is your (initial) connection times. And – since this is c/selfhosted – if you are setting a decent DNS cache in your local network, that should be even less of an issue.

    The only borderline scenario that I could see feasible, since this is c/selfhosted , is that some software you are setting up that requires nanosecond DNS resolution or somesuch sillyness is going to fail or report false errors. But why would you even do that?








  • The attack surface yes, but not the attack volume. No matter if the app is containerized or native, it has access to the data that it has to operate to. That’s literally part of computer nature.

    But a containerized app, assuming the container service itself is kept up to date, has less hooks to break into other stuff than a native app does. For starters, a native app can read everything that’s world-readable, which in a shared system might be lots of stuff but in a containerized app might be quite minimal.




  • Hopefully no one is asking developers to be virtuous (even tho, to be fair, if we are going to be asking that we should also expect the code to be wholly bugs-free!), but how many times they actually “keep their beliefs to themselves and focus on technical issues in the project”? On whichever side. It’s just not a thing that can reasonably be avoided all the time between humans.

    But the reality of these times is that behaviour outside the field of programming is representative and/or predictive of behaviour in the field of programming, when it comes to literally working with other people. And this is not only about the act of commiting changes or filing PRs, it’s about the why of programming and the ways of delivery as well. Someone who strongly associates with barbaric beliefs is less likely to want to spend their spare time working in peace for all, and more likely to be wanting to work on software that at least in some way carries or represents those beliefs, for example in capturing and using user data, or in aiding systems used by the military to kill children of “non-citizens”. So being “absolutely” uncaring does not really make sense.




  • What does “empathy in communication” have to do with a software project?

    Not having read Stein’s work, I can only mostly guess it’s related to the emphasis on the “communication” part as it applis to effective communication of duties, milestones, failure modes and reactions in a project. Torvalds’s tirades for example were awesome and most of the time well-deserved for the idiot trying to accidentally the kernel, but are quite more of a bummer and a momentum-killer when looked at at a project-wide scope.

    I’m all for empathy, don’t get me wrong, but ideally software projects are more focused on technical correctness than feels

    (Not) sorry to say, that age has long sailed. Remote teambuilding, capitalism and AI have made it that we now need to actually care and be watchful why or how something is being made to work, on the technical sense. Just look at the situation with Mozilla or Signal (offering systems that can be described as free, but are being offered so in a rather adversarial manner).