Erlang / Removing warnings when some behavior callback functions are not implemented?

The "best" practice is actually to implement stub callbacks, with sensible return values (such as {reply, ok, State} for calls {noreply, State} for casts and info etc.). This will also ensure stability and compatibility if someone would ever try a code upgrade, for example, on your code.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.