• 2 Posts
  • 1.05K Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • amio@kbin.socialtoScience Memes@mander.xyztemperature
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    7 months ago

    The focus of it is what you are used to.
    All scales are basically created equal - they must be, since they measure the same thing and scale the same way. (No pun intended.)
    The only difference there can ever be between C/K/F (or R for that matter) is multiplying by one constant and/or adding another.

    Yanks use Fahrenheit, grow up with it, and see it used every day. Therefore it is intuitive and logical. To them.
    The vast majority of people on Earth - about 95% - actually don’t, so it isn’t.

    That makes the phrasing and underlying assumption pretty characteristically American, and tempting to poke some gentle fun at.




  • amio@kbin.socialtoAsklemmy@lemmy.mlIs "female" offensive?
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    7 months ago

    I’d sneak a peek at some other league and do whatever they did.

    When I say “avoid using ‘female’” (specifically as a noun to mean “woman”) it’s not an absolute. The gist is just to not come off like a fedora-tipping twat. Sometimes it’s used intentionally to objectify or demean “females” in general, or using the “woman/female” distinction as some sort of pointed transphobic shtick.

    It’s still a perfectly cromulent word as long as it doesn’t get neckbeardy.




  • amio@kbin.socialtoAsklemmy@lemmy.mlIs "female" offensive?
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    7 months ago

    Male and female are biological terms. Mostly “man/woman” are more appropriate unless you’re specifically talking about biological sex. Particularly since a certain bunch of people is now using “females” with a bit of underlying vitriol, it’d be a good idea to stay away from it.







  • Because if you don’t keep a close eye on mental patients, some of them might hurt or kill themselves or other people - sometimes in extraordinarily resourceful and unexpected ways. It’s rare and overhyped, but the fact that it does happen means the system needs to account for it. Then add the usual amount of greed, incompetence, stigma etc., and suddenly the only way of accounting for that is, well, prison style.



  • Versioning. “This version of SharedComponent has this and that functionality” and “this version of OtherComponent requires this specific version of SharedComponent”.

    If you’re getting stuck with significant “this has to come with for that to go” problems - that aren’t literal dependencies, but arise from code wonk or poor separation of concerns - you may have some “architecture smell” that could be addressed. Obvious “usual suspects” include things (whether at a single class, component, or entire service level) that have too many responsibilities/purposes/reasons to change, and mismanaged abstraction.