• Huge waste of material on the label.

      Since the labels are larger, the boxes for those tea bags will need to be larger too. That incurs in additional waste of material and storage space.

      People working in markets selling those tea bags will complain. Now their boxes don’t fit in the aisle alongside boxes with tea bags of other brands.

      Customers will find it clunky and convoluted. Some will understand why the dev did it, and get angry - because from their PoV it’ll sound like the dev is saying “I assume that you’re a muppet, unable to distinguish the label from the bag”.

      And some will still do like others said: use a larger pot, fold the label, etc. Defeating the purpose of the change.

      There are plenty situations where you can be smart. This is not one of them, stick to standards and document it properly. “This is the bag, it goes in. This is the label, it goes out.”

      (Not that it changes much for me. I’m still ripping the tea bag apart and mixing the contents with my yerba mate. Unexpected use case!)

  • I design optics and I’ve seen a return request because they “couldn’t see the target” and included photos to show what they meant. The customer installed it backwards and didn’t bother trying the other way.

  • I can be an idiot every once and a blue moon. Thank you to anyone who put literally everything a manual just in case someone is braindead and isn’t afraid to rtfm.

    To be honest it’s just after I’ve spent 10 hours on something fairly complicated and new to me. I suddenly can’t think for myself anymore. It literally becomes a chore to do the simplest shit sometimes.

      • I do appreciate it, I know I’m no idiot.

        To be honest, I kinda wish some projects came with API manuals. I understand it’s not a priority in an open source project with limited resources.

        It would be nice to use a python based ml tool without passing commands through it via shell. People do it, I just don’t have the time or experience to analyze a complex project like ML voice synthesis.

  • A proper engineer would make the tag absorbent and use the principle of capillarity to transfer the water to the bag (and the other way round once tea flavoured) to cover this case.

    Users can’t avoid being stupid, but a proper engineer should be able to cover all cases.

    • So you’re saying it should wick the water from the cup to the table like an oil lantern. That seems like a good way to have half of your cup on the table.😂

      If you get it to travel up the string, gravity will definitely do the rest. It seems like such a passive aggressive way to design a product and I’m all for it.

  • If you have access to any kind of UX and UI folks, you automagicallly get a leg up on this, y’all. It is goddamn amazing.

    Single dev on a personal project? Go find someone in the community who has an eye for design or hit up a design forum. Work has you on a project with only two other devs and limited resources? Ask for a favor from the UX team down the hall.

    We are all tryna make good experiences out here. Let us avoid getting ‘teabagged.’

  • Speaking as a user (I’m not a programmer even if I’m often loafing around here):

    Left is not “optimistic” but “assumptive” - blame the dev and the user.
    Right is not “pessimistic” but “diligent” - blame the user.

    But the worst type doesn’t appear in this pic: they’d put a ball of chicken wire around the label so it’s physically impossible to put it in the hot water.

  • “I’ll add this to our knowledge base and other people can assist now!”

    “Hey So-and-so, it looks like you our are guru at this issue, can you take a look at these 4 users who mentioned the software in their ticket?”

    I just need to make progress on my projects, stop giving me desktop tickets pls :)