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
-
Tell them to imagine they have a long line of plastic balls, say 300 of them. They're all different colors.
They need to find the one that's a specific shade of green, so they take the color swatch and compare all the green ones, one at a time. Will they find it? Eventually, though they might possibly pick the wrong one that's very close in color.
Now tell them to imagine the same scenario, but the balls each have an ID number printed next to them. The ball number they're looking for is #289, so they look at the 11th ball from the end. Tada! There's the ball, and it matches the color swatch.
Oversimplified? Absolutely; but it perfectly demonstrates the need for unique id's.
Client from hell, next chapter.
As money comes in, project won't be canceled.
Only madness comes for free.
Newest insanity.... We had to explain that in a warehouse system a unique article number as an identifier is a must.... This discussion took 20 minutes.
The reason? Saving 2 secs as they don't have to enter the supplier item number....
Their plan?
Article Number can be...
Integer, automatically assigned
String, Supplier Name and Supplier Item Number seperated by a delimiter....
The argument that stopped this insanity... Costs.
We argued that if we are forced to implement something which we believe will be a high costs, no value, nonsense feature we won't do the necessary migration and programming after reversal as in 'find someone else who unbreaks this insanity'...
Did they understand that a warehouse system without article number for reference is dumb? Nope.
undefined