Elixir/Erlang Secure Coding and Deployment Hardening Guidelines

Nice! Does anything similar exist for handling user data?

Despite many laws exist now I still not see frameworks catching up on the docs re user data and privacy issues best practices.

Developers are still left alone. If you want to provide maximum user respect, ability to encrypt and potentially remove all user information you need to invent that wheel.

Probably one of the reasons why many open source projects have insufficient support for user data protection and handle user data in archaic ways.

How do you solve these problems?

Any good best practices / tips / frameworks for maximum user respect?

I wonder... why do the boolean coersion operators even exist since there are stricter (non-coersion) alternatives?

Granted, not providing an "if" would shock many people, but the "case" alternative isn't terrible.

But since this example is about misinterpreting return values (judging truthiness of :ok vs {:error, ...}), having explicit return types would solve this problem as well.

And not to start the war again, but as much as I admired Rich Hickey and his convincing talks, I am now a big fan of explicitly stated types for the clarity they provide the reader of a codebase. It's more of a chore to write, but it makes reading and understanding much better for me.