• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: August 14th, 2023

help-circle





  • Distributing power across a group of communities over the same topic (e.g. like seats in a congress/parliament) is a nice thought.

    However, my second thought was how vulnerable that is in a fediverse. To continue the analogy, an adversary could create new states (server/communities) of arbitrary population (accounts) at will.





  • In recreational climbing, skin calluses and surface abrasion aren’t usually much of a concern compared to tendon health. Skin heals light damage quite easily.

    However, it’s not uncommon for a new (or experienced) climber to develop their muscles beyond what their own tendons can take. Since it takes tendons so long to strengthen, it’s common to need managing the risk of finger pulley tendon injuries in climbing.

    Also, I do not know how these nuances apply in your context of your medical condition.


  • wanted to add something to the end of a for-loop, but had too little indentation

    To address this, I prefer reducing length & depth of nested code, so the for/while is rarely ever not visible along with everything inside it. Others have success with editors that draw indentation lines.

    opening up new/anonymous scopes

    I occasionally use Python nested functions for this purpose


  • I find it’s possible to operate Python as a statically typed language if you wanted, though it takes some setup with external tooling. It wasn’t hard, but had to set up pyright, editor integration, configuration to type check strictly and along with tests, and CI.

    I even find the type system to be far more powerful than how I remembered Java’s to be (though I’m not familiar with the newest Java versions).




  • In a sense, money represents all the future goods and services it can buy, and those goods and services ultimately resolve down to someone’s time and effort. Money was conceived as a formalization of IOU’s, after all.

    So it’s similar to asking whether there’s a limit to how much time and effort from (i.e. influence over) others one would want.





  • I think people are being lazy, in a selfish, tragedy of the commons sort of way.

    When standing in line, they all watch the customer stand there doing nothing as the cashier checks out items. If only they’d bag their own things, we’d all be able to get on with our lives that much sooner. Instead, they continue standing there doing nothing, as the cashier now bags their items.

    Then the next person in line moves up and also just stands there, also unwilling to do anything to help speed things along.


  • Kache@lemm.eetoProgrammer Humor@lemmy.mlGit Rules
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    10 months ago

    avoiding merge conflicts

    No, not like that – you misunderstand. I’m not talking about actively avoiding conflicts. Coordinating to avoid merge conflicts is the same work as resolving a merge conflict anyway, just at a different time.

    I’m talking about creating practices and environments where they’re less likely to happen in the first place, never incurring the coordination cost at all.

    One example at the individual level is similar to what you mentioned, but there’s more to it. E.g. atomically renaming and moving in separate commits, so git’s engine better understands how the code has changed over time and can better resolve merges without conflict.

    But there’re other levels to it, too. A higher-order example could be a hot module where conflicts frequently occur. Sure, atomic commits and all that can help “recover” from conflict more easily, but perhaps if the hot module were re-designed so that interface boundaries aligned with the domains of changes that keep conflicting, future changes would simply not conflict anymore.

    IMO the latter has an actual productivity benefit for teams/orgs. Some portion of devs just aren’t going to be that git proficient, and in this case, good high level organization is saving them from losing hours to incorrect conflict resolutions that can cause lost work, unintended logical conflicts (even though not lexical conflict), etc. Plus, it implies abstraction boundaries better match the changes demanded by the domain, so the code is likely easier to understand, too.