Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "foolproof"
-
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
-Douglas Adams1 -
Useless feature I've built?
Too many to mention. Here's #25.
Modified an existing "Are you sure..?" dialog pop-up (Yes/No buttons) to Yes/No/Cancel. Why? Managers claimed users were "accidentally" clicking 'Yes' when they should have clicked 'No' and causing all kinds of chaos, costing the company money, etc. Managers believed giving the user two chances instead of one would make it easier to avoid the problems they caused.
The meeting:
Me: "Users can click 'No', hit the 'Esc' key, or click the close 'X' button on the window, how will an extra button make it more foolproof?"
Mgr1: "It just will. Andy accidentally deleted inventory and when I asked him if an extra button would have saved them a days worth of re-counts, he said yes."
Mgr2: "Barb accidentally credited a customer $1,500. She promised me she clicked 'No', but the system credited the account anyway. An extra button would have saved us thousands of dollars!"
Me: "Um...these sound like training issues, not an extra button issue."
MyMgr: "PaperTrail, how hard is it to add an extra button?"
Dev1: "Oh yea, adding buttons is easy."
Dev2: "I can do it 5 minutes"
Dev3: "We'll save the company thousands and thousands of dollars!"
<lots of head-knodding and smiles>
MyMgr: "That settles it. PaperTrail, add the extra button!"
Users still screwed things up, but at least they couldn't blame it on not having an extra button.24 -
analysing a database problem and writing a 4-line fix: 5 minutes.
preparing a foolproof manual for the manager on how to apply the fix: 15 minutes
writing a manager-level explanation what the fix does: 30 minutes.
explaining it to the manager: 30 minutes.
writing a _detailled_ explanation why we need the fix: 60 minutes.
explaining it to the manager again: 30 minutes.
figuring out why our progress is slow:
_priceless_6 -
I feel all of us here could use this brilliant quote by Douglas Adams.
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.1 -
For several years now, I have been writing programs for myself. I have been publishing the source code for them, but none of them ever got much traction. Then I wrote a program that existing users on social media could just interact with without installation (because even that is too much apparently).
When I wrote the programs for myself with others secondary, I had logic problems to solve and dealt with fucked up API's. Now I still have that problem, but I also have to deal with user retardation. They are not using the program in the way I wrote it to be used, at all. They are not passing arguments where there should be, they are running commands that are still under development and therefore (rightfully IMO) available to only me. I am the one being blamed, why doesn't this thing work?
I'd like to rephrase their question to me. Why are you user not using the goddamn program properly? Why should I need to make half the goddamn code account for users' sheer level of retardation?
Yes, users are retarded. And it's not a battle we can win. Earlier I heard this saying that "every time you make your tools more foolproof, the universe invents a better fool".7 -
If you think parametised queries will save the day think again.
I occasionally test sites I visit throwing a few quotes at inputs and query params.
I also always test logging in as % with user or pass.
Not only are plaintext passwords a thing but so is this:
WHERE username LIKE ? AND password LIKE ?.
Once I saw an OR.7 -
How much of fairness can human factor add to a government compared to foolproof AI algorithm. Is it too early or too utopiaic to trust AI with governance compared to agenda based corporate embracing environment destructing corrupt to the core politicians. Is AI more evil than today's politicians. Is there a project already similar to crypto currency on governance. On seeing all butt heads in power and in age where whistle blowers are caged I feel helpless tothink software cannot change the most primal thing - politics. Switching on TV and watching news had never been this disgusting. Flushing these thoughts , came back to my desk to learn something better and be at peace with programming.4
-
Does anyone know a foolproof way of radio controlling a dozen arduinos? I'm working on a big project that needs about a dozen arduinos working with each other.16
-
I'm sure this will have no privacy or security implications whatsoever. 100% foolproof and not a problem.
https://cnn.com/2020/11/...1