• 1 Post
  • 1.22K Comments
Joined 3 years ago
cake
Cake day: June 29th, 2023

help-circle

  • It’s actually good UX practices to do this. You light up a path to get a result (pressing the start button to continue to the menu), and then a large segment of people will continue to press start, even if they’ve previously stumbled upon the fact that any button will work

    It’s like picking a home server in the fediverse. You can tell them it doesn’t matter what they pick, but a lot of people will be intimidated and nervous about having to make the choice. It’s a major problem for adoption

    You also don’t have to tell computer minded people inconsequential rules, they’ll figure it out themselves pretty quick

    So by choosing an arbitrary button for the instruction, you remove a meaningless “choice” that genuinely lowers the friction for a large chuck of the population

    There are also people who, if you tell them to press any key, they will happily mash the function keys and be confused and upset that unexpected things are happening

    There’s even a select few who will physically look for the any key every time just to make sure it’s not suddenly been added to their keyboard, and there are even the special few that will hit the power button and get angry because they think you’ve caused them to break their computer

    Some of these people have higher degrees too…I didn’t believe it until I saw it for myself



  • What you’re saying is more consistent, but I don’t think it’s more readable

    I’m fine with let or var…if the compiler is going to infer the type thats all well and good. But it’s a replacement for the type - why would you write both? It should be either or

    And if the type is being inferred, the next thing I want to know is where it came from. That tells you the type and more, I don’t want to have to see a type name that may or may not be there









  • theneverfox@pawb.socialtoLemmy Shitpost@lemmy.worldIt hurts
    link
    fedilink
    English
    arrow-up
    1
    ·
    21 days ago

    People want cheap products in a general sense, they don’t like off shoring, it was hugely disruptive to jobs and the quality nose dives (at least for a time, sometimes permanently). They didn’t ask for or choose it, they’re the low information side of the system

    Of course they’re upset at things being tariffed, they don’t want prices going up. They likely have some preference to buy things made locally, or by a country with a reputation

    None of this is a choice made by consumers, it’s a generalized set of incentives and pressures created by the market

    It’s like planned obsolescence… People hate it, it’s being sold to them




  • …Isn’t that what we’re talking about though? Or did I misunderstand the OP?

    The post said they were neon database creds, so I would think those would live on the production system in .env

    Rereading it, it seems that they probably set their local build to point at the prod database… Which is like halfway developing (with AI) in prod (which I think we’d agree is not ideal)

    I do absolutely agree with what you’re saying though, not everyone should have access to the prod system for sure… Especially not an AI on a loose leash

    I’d split the difference and say we’re both right