4 ms·
I saw a case a few years ago where the management of a company I knew were worried that the sales team were covering their mistakes and lying about it to blame
by aidos 9y ago
I saw a case a few years ago where the management of a company I knew were worried that the sales team were covering their mistakes and lying about it to blame the (external) dev team's code. They asked me to take a look into it one morning.
At first glance there didn't seem to be a lot to go on. There was no auditing in the application itself so I focused on the nginx logs. It's amazing how clear of a picture you can create from ip addresses, user agent strings and accessed urls.
Within an hour I could say with a high degree of certainty that the story was something like:
Sales rep makes mistake with record on Friday afternoon
Monday morning - at home, late for work
Receives call from another rep re mistake
Logs in via mobile device to see the issue
Logs in via desktop to fix broken record
Arrives at work 1.5 hours later
Claims dev team had broken the record for the weekend
There's a lot of information lurking in log files (let alone insecure dbs), and that's just the tip of the iceberg of what's stored these days. I dread to think how much personal information is stored in some of the bigger CRM apps these days.
Quite frankly I'm glad there's a push to start thinking about this stuff from the outset at the moment.
- pcarolan 9y agoI think the bigger problem was the culture that company had in place that would lead people to do that.
- aidos 9y agoAbsolutely! Then again, no more broken than a number of other places I’ve worked over the years. I could write a book on that subject :-)
- beagle3 9y agoSometimes it's just what the people bring with them, even if the company has "good" culture (whatever that means). And even in companies with the best culture, I would expect such things to happen if the cost of a mistake is comparable to a person's yearly salary or above that.