• 0 Posts
  • 202 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.


  • I feel like all public servants (including cops) ought to have public liability insurance, where money would end up coming from in these situations, which then the employer (police department, other department) needs to pay, the employee is aware of, and is part of their renumeration (i.e. the more their premiums cost, the less they’re making), making idiots more of a financial liability to themselves.

    Quite quickly you’re going to have people acting as responsibly as possible if you’re insurance premiums then go up when you act like a moron.

    Obviously this would require protections so that people don’t end up being screwed over by insurance premiums, but still, this seems to be an issue in public service all over the world, no consequences because the tax payer just ends up footing the settlement, and the public servant goes on their merry way.


  • 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: 🔥🔥💥















  • (Pressure) * (volume) = (# moles) * (gas constant) * (temperature)

    The ideal gas law.

    In another thread I admit I didn’t explain my position here well enough. I would only not explain this equation given sufficient context (e.g. I’ve shown all those variables in a table, and my intended audience is people familiar with basic chemistry, which I’d expect would be everyone reading the report for this particular example, since this is high school chemistry, and the topic of all reports I work on is chemical engineering.)

    People can read the conclusions if they’re not familiar with chemistry, and for the detail, they’re not my intended audience anyway.

    Generally I still hold the position that you should define variables as much as possible, unless it’s overly cumbersome, given your intended audience would clearly understand anyway.

    In context this simple equation is obvious even if you change the symbols, as long as there is sufficient context to draw from.


  • No worries friend, no hard feelings and appreciate the engagement!

    Yeah, agree it is a bit wishy washy in terms of gauging how much explanation to include ¯_(ツ)_/¯

    I suppose (in my opinion) the mindset should be: include as much explanation as possible, without it being cumbersome.

    I personally err on the side of over-explanation and have had some senior engineers give me feedback that it’s too much. Still learning for myself how much is too much.

    Totally agree though, that there are many cases where people leave things out as assumed, when it’s not really reasonable to do so.

    A side-thought on specificity: one of my biggest pet peeves is when people list pressure with the units of kPa, when they really mean kPag. In industry, you are rarely talking in absolute pressure (other than for pressure differences) and people then get lazy/don’t know/assume it’s fine to do something like: set point 100 kPa (when they mean 100 kPag). It isn’t fine though, because at lower pressures atmosphere counts for a pretty large percentage of the absolute value.