Point free debugging
<p>So we're using the very nice <a href="http://ramdajs.com/docs/" rel="noreferrer">ramda</a> library at work, which is great because we're able to use a largely point-free style of code. The problem with this is that there are far fewer places to look when things go wrong that point to something in our code; most run time errors occur because of a misuse of composed ramda functions. Combine this with passing these functions to a framework that uses a lot of redirection (we're on react/redux), and often when something goes wrong, it's deep in library-only code, and it's very hard to find out where I went wrong.</p>

<p>Is there any way to mitigate this problem without moving away from point-free style?</p>