[mondaygreens]

The outcome of such approach is very few surprises when running the code, because the code behaves how you think it should behave.

And when it doesn't, you know exactly where to look to find the problem and often its solution.

For me that's the biggest payoff of reading the documentation or skimming it multiple times, it's a huge time saver when things inevitably go wrong.

Then there's also the ability to think within the whole scope of the lib as opposed to the specific thing you pulled it in for.

[supr_strudl]

Exactly this.