Job: cashier
Item doesn’t scan
Customer: “That means it’s free, right?”
🙄🙄🙄🙄🙄
Only about 4 weeks in as a cashier and I’ve heard this enough to last me a lifetime.
Job: cashier
Item doesn’t scan
Customer: “That means it’s free, right?”
🙄🙄🙄🙄🙄
Only about 4 weeks in as a cashier and I’ve heard this enough to last me a lifetime.
When someone doesn’t understand a process and asks “can’t you just do XYZ?” Usually management. “Just” is actually a 2 week project and tons of hours and trouble shooting
Can’t you automate around this edge case that we told you during planning could never happen due to controls on our end?
That’s easier for us than sticking to our word.
What do you mean that it was a key requirement of your design, like you told us in advance?
I’m currently in a software development project which was handed over to a different department with little software development expertise, and fucking hell, I hear this so often.
Can’t you just run the tests against against a database like normal? Why do you need to automate the setup of this database? (I do not know what “normal” means, they did not elaborate.)
Can’t you just switch over all the code to go directly against the database rather than also supporting in-memory.
And then five minutes later: Can’t you just hook up the database connection where we need it and use in-memory for the rest?
Like, I’m trying to appreciate the critical questions, because hey, maybe there is something I’m missing. But always this “just”, and them being dissatisfied when you tell them it doesn’t make sense or would be more work, that’s what kills me.
Developer I used to work with had a policy where if anyone said “just do something”, they were now the sole person responsible for implementing it.
“Just redo the front end in react”. “Cool. Thanks for volunteering”