Hmm ... Better pigeon hole clients into only using the teabag.
"Why can't I put the label in the water?!"
this post was submitted on 11 Aug 2024
1214 points (99.0% liked)
Programmer Humor
19817 readers
82 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Our legacy system always puts the label in the water and our clients rely on the faint cardboard flavor.
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?
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()
load more comments
(3 replies)
What's this from?
gravity falls
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.
If it can be mounted both ways it should work both ways. 🤷♂️
And that's how an iPhone with an interface that even a toddler can figure out sold a few billion units.
At what cost, though? I thought the generations after the millennials would be more tech-literate. But after seeing Gen Zs around me at home and at work, things are just regressing.
It was inevitable. We took a mishmash of things that kinda worked together with a patchwork of software and shoved it into a streamlined define with a custom made interface to tie it all together. One of those things pushes the user to learn more, and it’s not the finished and polished product.
Can't really blame them either, it was our generation that dropped the ball in making sure they were more tech literate than us. Not that I have kids but still.
Nah, our generation had to tinker with shit to get it working. Kids these days have it easy, which is good from a user perspective, but fails to train them how any of it actually works at a deeper level.
No one has to install a device driver anymore.
load more comments
(1 replies)
load more comments
(3 replies)
As someone who's used and uses both for work and isn't a fanboy of either, sorry but apple does not have an easy to learn interface. It seems like every single choice they made was done to just be different from the alternative, more often than not to the detriment of the user. If they lock people in to how their ecosystem works low tech people can't easily change.
load more comments
(5 replies)
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.
This assumes an infinite timeline and budget.
Well, no proper engineer will agree to less than that
load more comments
(1 replies)
No, that complicates things way too much. Simplicity in design is beauty. A real engineer would recognize the tag on the string not only as a point a confusion, but also a superfluous feature. Simply remove it. The end user will have to use a spoon supplied by themselves to remove the teabag, but thats their problem. At least there is actually tea in the cup at that point.
load more comments
(2 replies)
load more comments
(2 replies)
Idiot proofing just results in a better class of idiot.
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.
Send multiple all user emails stating which end to put in the water. People still call the Help Desk or email you directly, your response is forwarding them the email, they complained that it's not convenient or they get too many emails or don't have time for emails.
You send documentation and place it on the portal. they complain it's overly complicated, so you add screenshots with which end to put in the water. They still mess it up and complain about lack of instruction.
You schedule 30 minute courses, 3 times a day, every day of the week and spam out notifications to sign up. You get a total of 12 people the first 2 weeks, most of which figured it out on their own at some point but thought it was mandatory, or that there were high level secrets or Tips n Tricks you were gonna teach. When the education period ends, you still get people complaining that the times weren't convenient enough for them because they work 2nd shift or weekends.
You schedule another 2 weeks of classes, after hours and on weekends. 2 people show up, but not the ones who bitched about it.
Despite everything, your boss still sings you on your review didn't meet the needs of the organization with this rollout
Oof, I’m not in IT thank goodness, but I still feel this in my bones. I’ve had to write plenty of instructions for in-house trained users though, and it seemed just as bad. I can’t imagine what it’s like with real randos.
I’ve definitely seen some of these “please let us help you” getting sent around. And even in completely different types of organizations I’ve seen time and time again how the obnoxious entitled complainers don’t even show up.
load more comments
(2 replies)
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.'
Basically you have to hide all choice behind a settings page. Think of a cattle chute that only let's them go one direction to the bolt gun. Wait...
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'm not a programmer yet even if I'm often loafing around here
Fixed that for you...
Join us on the dark side. We have cookies.
Clicks Accept Cookies
load more comments
(2 replies)
I write graphics software that almost seems intuitive, until you realize I gave it a split personality.
Even I forget about the split personality side of it.
if ( parameters.teaMass <= TEA_BAG_WEIGHT ) {
return "Error: incorrect input. Check if tea bag was inserted correctly into water container."
}
load more comments
(1 replies)
I'd* better write some documentation
Using better by itself is fine in an informal context, and "had better" is only required for formal contexts. And I don't think a meme on the internet counts as a formal context.
And also, 🤓☝️
That'd be a contraction of 'would' in this case, wouldn't it? As an ESL speaker I used to find these grammar 'mistakes' (for lack of a better word) made more difficult for me to parse the sentences. As with code 'written once but read many times' would apply here.
For a lot of English speakers, the "had" and "have" in contractions is completely omitted in certain contexts. It's more prevalent in some dialects (I'm in the south US and it's more common than not). Usually "had" is dropped more than "have".
Also, English can drop the pronoun, article, and even copula for certain indicative statements. I think it's specifically for observations, especially when the context is clear.
looking at someone's bracelet "Cool bracelet." [That's a]
wakes up "sigh Gotta get up and go to work..." [I've]
"Ain't no day for picking tomatoes like a Saturday." [There]
"No war but class war!" [There's]
"Forecast came in on the radio. Says there's gonna be a hell of a lot of rain today." [It said -> Says/Said]
"Can't count the number of Brits I've killed. Guess I'm just allergic to beans on toast." [I; I]
"House came tumblin' down after the sinkhole opened up" [The]
"I'd" can be "I would", mainly if used with a conditional or certain conjunctions/contrastive statements (if, but, however, unfortunately). Also when preceding "have" – e.g. "I'd have done that". Because "I had have" doesn't make sense, nor does "I had " anything. "I'd" as in "I had" is followed by a past participle.
"I'd" is usually "I had" otherwise, forming the past perfect tense. But in "I'd better", it's a bit confusing because "had better" is used in a different sense – the "had" here comes from "have to" (as in "to be necessary to") and can be treated as both a lexical verb and an auxiliary verb. "had better" is a bit of a leftover of more archaic constructions.
It would be a contraction of had: "I had better write..." Using would there doesn't make sense.
load more comments
(1 replies)
load more comments
(3 replies)
I don't even work in IT but I make complex Excel tools for my Finance team.
I get an email about once every week or two from one of my coworkers asking what to do about an issue. Nearly every single issue would have been resolved if they just read even the first few instructions.
My favorite is a specific tool we use to review the financials. It relies on Scripting.Dictionary which is only present in .NET 3.5.1 or prior. The very first instruction on the file says you need to download it. There's even a very handy button right there which will take you to our software center to install it.
Yet every single time someone gets a new laptop, they immediately assume that the file is broken.
If you hear about it that much, why not make the script check for .NET before crashing?
load more comments
(1 replies)
You're calling this person stupid, but they're 90% of the way to getting it right.
If only every technical problem was this easy to solve.
"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 :)
view more: next ›