no amount of documentation can save users from themselves
no amount of documentation can save users from themselves
no amount of documentation can save users from themselves
You're viewing a single thread.
Smart developer: let's make the label an 8 inch square so it won't fit in any mug.
End user: makes tea in a large pot, to fit the label.
Developer: THATS IT WE’RE A BROWSER BASED APP NOW!
End user: why can’t I run this on my AOL account?
Omg that's gold!
User: Folds square in half to fit into mug.
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!)
tea_bag.unwrap()
Just get rid of the label altogether. I'm always suspicious when a teabag has a string on it.
You aren't supposed to leave it in the water the whole time.
Not a problem if you're using a teapot, or for a mug you can use a spoon or just your fingers