A huge part for me is how they handle employees and how that makes employees steal things.
My wife ordered an iPhone and we received a salt mill and a flashlight. Called them, they said sorry send it back. But then they would not return the money cause we did not return the phone. At that point Amazon accused us for betrayal and forced us to take a lawyer to get parts of the money back.
That was our last day of using Amazon or prime video.
My washing machine displays a remaining time when you start it but is constantly wrong. So you go to the basement to find out it needs 15 more minutes. You go down 20min later and still 5min left. It is very pleasant to know when it is ready without going to the basement
And even if not, your CI tests take hours to run because of all the network calls.
Automated tests that do real calls to 3rd party services are essential too, but they should almost never be part of your standard CI scripts that get triggered by every push.
But I think the article was mostly talking about mixing network/http level mocking with business logic tests, which I'd admit isn't always ideal, but IME complex test cases often require some level of compromise.
My wife ordered an iPhone and we received a salt mill and a flashlight. Called them, they said sorry send it back. But then they would not return the money cause we did not return the phone. At that point Amazon accused us for betrayal and forced us to take a lawyer to get parts of the money back.
That was our last day of using Amazon or prime video.
reply