• 1 Post
  • 107 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • While I know that these days, bugs in code can cause real-world harm (personal info leaks, superannuation records lost, lol google), I find it humorous to think of the equivalent, even worse outcomes in my discipline (chemical/process engineering).

    “Didn’t do any checks, fuck it, I know this calculation is fire 🔥”

    Later: 🔥🔥💥



  • Thing is, you usually define all your variables. At least we do in engineering (of physical variety, rather than software).

    Mostly because we can’t expect everyone reading the calculation to know, and that not everyone uses the same symbols.

    Not explaining each variable is bad practice, other than for very simple things. (I do expect everyone and their dog reading a process eng calc to know PV=nRT, at a minimum).

    Just like (in my opinion) not defining industry specific abbreviations is also bad practice.

    Mathematicians don’t do this? Shame on them.


  • It would make sooo much more sense for the ISO to set something up, and make governments each responsible for keeping it updated, since they’re the ones doing the changing.

    Require all participants to amend their law/regulations, so there’s a note to prompt whoever is in power and changes it next.

    I’m sure some places would still neglect to do it… Haha





  • The drawbacks are many and the benefits are few.

    Watching foreign films would be a pain, where is this in the world again, what does 19:00 mean for them? More exposition, or you just have to guess based on languag and accent.

    I need this work done by our team in XYZ country, what are their working hours? (wow, look at that, still using timezones?)

    When you arrive somewhere on holiday, now you have to get a sense of the time there. Or continually be thinking “what’s that in my home time?/what’s that in solar time”, which is why solar time just makes more sense.

    People aren’t going to stop thinking in solar time, ever. We’re hard-wired to be awake with the sun. It doesn’t matter what the numbers are, you will associate them with the sun. The question then becomes, would we rather all use roughly the same numbers (timezones, what we currently have), or different numbers (everyone using UTC).

    Using UTC solves only 1 problem, you can say verbally to someone across the world, let’s make the meeting 15:00 - but this is already easily solved by using a calendar which converts for you…

    There’s a reason we have never used a single non-solar time, it’s just worse and I think there’s a reason these posts always end up on programmer focused places on the internet. Yes, I’m sure their job is annoying, and it would be easier to not have to solve time conversion problems, but the time conversion problems wouldn’t even go away if you forced everyone to use UTC. You’d just start having to do conversions to solar time, or looking up waking hours (which is just timezones)

    This is a solved problem.


  • MisterFrog@lemmy.worldtoProgrammer Humor@lemmy.mlGot no time to code
    link
    fedilink
    arrow-up
    40
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Problems caught early are much easier to fix than problems caught later. This applies to any project (I’m not a programmer, but an engineer in the traditional sense).

    Just “doing it” without coordination and review is a great way to waste a bunch of effort down the line with re-work.

    Edit: typo












  • Apparently this included on some phones running GrapheneOS according to some other commenters.

    I agree with your sentiment, but think we need to urge our governments to regulate the ever-loving god our of these companies.

    It’s getting more out of hand, and I don’t think we should just resign ourselves.

    Flashing GrapheneOS is not an option for the vast majority of people due to barriers to entry, and potentially essential banking apps not playing nicely.

    I’d rather not move on. Heck 'em.