4 ms·
I never assume that “settings” guarantee what they claim. It’s just not practical even with good intentions, for a single non-public code base. As a developer
by makecheck 8y ago
I never assume that “settings” guarantee what they claim. It’s just not practical even with good intentions, for a single non-public code base.
As a developer, I know it is hard to implement something once, harder to implement consistently across multiple interfaces, and damn near impossible to keep correct years later after employee turnover and other twists.
The sad thing is that it costs a ton more money to do things really well, and companies can basically take advantage of the low price of doing things poorly until finally forced. And by then, they have tons of money so they can comply but any startup is screwed because now it costs more for everyone, even those entering the game.
- gbumakefan 8y agoThis bug is just another example of the Valley children doing what they do best - writing terrible code. Keep moving fast and breaking things, kids. Please keep your culture confined to the west.
- jdc0589 8y agoeven moreso when you remember that SO MANY COMPANIES enforce most of their auth z/n at the edge, and are a lot looser between internal services