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

help-circle





  • Luckily/unluckily (because effort), in Australia, consumer guarantees on length of time you can get a refund are vague.

    E.g. it doesn’t matter that a fridge’s manufacturer warranty is only 2 years, you expect that to last longer.

    With effort, you could probably get a fridge fixed like 5 years after purchase with some badgering / threatening small claims.

    Bricking your product would probably fall under that category.

    This is wild speculation, not a lawyer.


  • 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