3 ms·
I've also seen plenty of projects which did not use proper authentication and authorization because devs were too lazy to implement it or to learn the platform
by isbvhodnvemrwvn 5y ago
I've also seen plenty of projects which did not use proper authentication and authorization because devs were too lazy to implement it or to learn the platform they were developing on (e.g. AWS). It's an indirect effect on privacy, but when it hits it hits hard.
- c1ll1an 5y agoFair @isbvhodnvemrwvn - I'd say it's a combination of laziness, lack of knowledge perhaps or both? I'm conscious that it's easy to say "do _____ better" and insert a soap box like privacy or security; but if you don't provide developers with tools, whether that's libraries, IDE plugins, linters or code analysis tools to make that task easier, it's almost impossible - can't ask developers to be privacy experts, but we can help them to make that expertise readily available. Like the example you took - provisioning cloud infrastructure is a heck of a lot easier now that it was a decade ago because of a bunch of orchestration and infra as code tools that ease the burden/knowledge gap for developers. We've got to have the same for anything we care about - in my case, that's privacy.