Just this guy, you know?

  • 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • zaphod@lemmy.catoLemmy Shitpost@lemmy.worldPlease Stop
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    4 months ago

    You didn’t actually read the page you linked to, did you?

    Let’s just jump to the conclusion:

    This author believes it is technologically indefensible to call Fossil a “blockchain” in any sense likely to be understood by a majority of those you’re communicating with. Using a term in a nonstandard way just because you can defend it means you’ve failed any goal that requires clear communication. The people you’re communicating your ideas to must have the same concept of the terms you use.

    (Emphasis mine)

    Hint: a blockchain is always a Merkel tree, but a Merkel tree is not always a blockchain.


  • zaphod@lemmy.catoLemmy Shitpost@lemmy.worldPlease Stop
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    8
    ·
    edit-2
    4 months ago

    the technology itself has its use cases.

    Cool.

    Name one successful example.

    I mean, it’s been, what, 15 years of hype? Surely there must be a successful deployment of a commercially viable and useful blockchain that isn’t just a speculative cryptocurrency or derivative thereof, right?

    Right?









  • zaphod@lemmy.catoProgrammer Humor@lemmy.mlThis is painfully true
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    4 months ago

    There are more beginners then there are experts, so in the absence of research a beginner UI is a safer bet.

    If you’re in the business of creating high quality UX, and you’re building a UI without even the most basic research–understanding your target user–you’ve already failed.

    And yes, if you definite “beginner” to be someone with expert training and experience, then yes an expert UI would be better for that “beginner”. What a strange way to define “beginner” though.

    If I’m building a product that’s targeting software developers, a “beginner” has a very different definition than if I’m targeting grade school children, and the UX considerations will be vastly different.

    This is, like, first principles of product development stuff, here.


  • zaphod@lemmy.catoProgrammer Humor@lemmy.mlThis is painfully true
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    4 months ago

    Unless you’ve actually done the user research, you have no idea if a “beginner friendly UX is a safer bet” . It’s just a guess. Sometimes it’s a good guess. Sometimes it’s not. The correct answer is always “it depends”.

    Hell, whether or not a form full of fields is or isn’t “beginner” friendly is even debatable given the world “beginner” is context-specific. Without knowing who that user is, their background, their training, and the work context, you have no way of knowing for sure. You just have a bunch of assumptions you’re making.

    As for the rest, human data entry that cannot be automated is incredibly common, regardless of your personal feelings about it. If you’ve walked into a government office, healthcare setting, legal setting, etc, and had someone ask you a bunch of questions, you might be surprised to hear that the odds are very good that human was punching your answers into a computer.



  • zaphod@lemmy.catoProgrammer Humor@lemmy.mlThis is painfully true
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    4 months ago

    That third screenshot, assuming good keyboard navigation, would likely be a godsend for anyone actually using it every day for regular data entry (well, okay, not without fixes–e.g. the SSN and telephone number split apart as separate text boxes is terrible).

    This same mindset is what led Tesla to replace all their driver friendly indicators and controls with a giant shiny touchscreen that is an unmitigated disaster for actual usability.