Hmm … Better pigeon hole clients into only using the teabag.
“Why can’t I put the label in the water?!”
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.
And that’s how an iPhone with an interface that even a toddler can figure out sold a few billion units.
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.
Honestly, if you read the manual you are very much not dumb
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.
This assumes an infinite timeline and budget.
Well, no proper engineer will agree to less than that
