5 ms·
Not only that but a cheap, inexperienced dev can create negative value. Not just in the product that they're working on but your entire brand. Just ask LinkedI
by riskable 10y ago
Not only that but a cheap, inexperienced dev can create negative value. Not just in the product that they're working on but your entire brand.
Just ask LinkedIn or Yahoo if it was a good idea to put some ignorant fool in charge of the system that stored passwords. Aside: I'm sure that person is worth more now because they won't make such mistakes (again)!
Rant: Looking towards the future I want to know which ignorant fools are in charge of Microsoft's Active Directory product that is currently shipping with the same damned ignorant mistake (no salt). I mean, seriously guys: How can you allow the product to continue with such a blatant disregard for basic security?!
Microsoft is going to be the next LinkedIn if they don't fix it.
- uremog 10y agoBad chefs create negative value just as easily. Wasted ingredients. Bad product that looks ok and leads to unhappy customers. Etc.
- yomly 10y agoPoor hygiene leading to food poisoning too
- jobu 10y agoThis comment made me think of Chipotle. I haven't eaten there since all the food poisoning problems. Chipotle is a big chain and got national attention for the poisonings, but in the age of Yelp a few people getting sick can tank a small local business. Better to pay a little more for decent employees that care about their job and also give them benefits so they don't come in sick and spread disease.
- uremog 10y agoDon't you think it's likely to be a supply chain problem in this case though, seeing as multiple locations were affected simultaneously?
- zanny 10y agoCheap, inexperienced pastry chefs can also ruin a restaurants reputation if they screw up too badly. You get the quality you pay for.
- riskable 10y agoAh, but a pastry chef can only disappoint so many customers at once. A single stupid mistake by a software developer can impact millions. The Yahoo leak alone was half a billion users. That's a lot of dough!
- jethro_tell 10y agoWhat do you mean? I don't believe there was much indication that that cost yahoo anything at all? The stock didn't respond. I doubt many customers left. The page rank has not changed. And there is no indication from previous large breaches that the customer cares or at least thinks anyone else is doing it better. So what leads you to think that the impact to a business (especially of comparable scale) would cause more financial impact if it was your average dev job vs a chef?
- shagie 10y agoThe stock was being held up by Version's offer. They've asked for a discount of 1B, and are considering backing out altogether. The stock will probably respond then. > "We're looking to Yahoo to demonstrate to us the full impact they believe it's not," Silliman said. If Verizon concludes the breach had a material impact on Yahoo's business, then a key condition of the deal would not be met, he said. https://www.washingtonpost.com/news/the-switch/wp/2016/10/13/verizon-just-raised-a-big-warning-flag-for-yahoo/ https://www.washingtonpost.com/news/the-switch/wp/2016/10/13...
- emodendroket 10y agoYeah, Yahoo was already dying of attrition anyway. I suspect the majority of those accounts were not active.
- vonmoltke 10y ago> Not only that but a cheap, inexperienced dev can create negative value. Not just in the product that they're working on but your entire brand. > Just ask LinkedIn or Yahoo if it was a good idea to put some ignorant fool in charge of the system that stored passwords. Aside: I'm sure that person is worth more now because they won't make such mistakes (again)! Why are you assuming the problems of Yahoo and LinkedIn were caused by cheap, inexperienced developers? From my experience I think the problem was more likely that someone implemented a basic, not-for-production system to scaffold the larger system and was not permitted to change it by management that demanded it be released yesterday.
- kafkaesq 10y agoJust ask LinkedIn or Yahoo if it was a good idea to put some ignorant fool in charge of the system that stored passwords. Ultimately, the "ignorant fools" responsible for such mishaps are almost always at the management level.