• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • This isn’t a new thing but I hate anytime it asks me a question. I’ll be driving through an accident scene trying to work out where the cop directing traffic wants me to go and if I’ll need to go a different way because the turn I was gonna make is blocked off and at that precise moment google maps decides it’s a great idea to cover the bottom half of the screen with a “is tHeRe sTiLl An aCcIdEnT hErE?”

    If it’s illegal to use your phone while driving it should be illegal for navigation apps to suddenly require interaction in the middle of navigating.







  • I think we also need levels of PII or something, maybe a completely different framework.

    There’s this pattern I see at work where you want to have a user identifiable by some key, so you generate that key when an account is created and then you can pass that around instead of someone’s actual name or anything. The problem though, is that as soon as you link that value to user details anywhere in your system that value itself becomes PII because it could be used to correlate more relevant PII in other parts of your system. This viral property it has creates a situation where a stupid percentage of your data must be considered PII because the only way it isn’t is if it can be shown that there is no way to link the data to anybody’s personal information across every data store in the company.

    So why is this a problem? Because if all data is sensitive none of it is. It creates situations where the production systems are so locked down that the only way for engineers to do basic operations is to bend the rules, and inevitably they will.

    Anyway, I don’t know what the solution is but I expect data leaks will continue to be common passed the point when the situation is obviously unsustainable