As I've attempted to help people learn things over the years i've noticed some patterns and anti-patterns that people have when learning things, for example in the context of haskell I wrote just now in the fp chat slack (edited a bit):
regarding the whole issue of"getting the answer and using it but not understanding it" vs "getting an answer and really understanding it"
i think part of succeeding as an engineer is once you have gotten a piece of code shown to you you are able to take it apart and understand it
effectively and then internalize it and also go meta and think "ok, why did I have to ask a question about this in the first place? what do I need to get
better at in order to become the person answering questions, not asking them?"
because "there is more happiness in giving than there is in receiving"!
As I've attempted to help people learn things over the years i've noticed some patterns and anti-patterns that people have when learning things, for example in the context of haskell I wrote just now in the fp chat slack (edited a bit):