Information foraging: the tricks great developers use to find solutions

<p>You can check out some more of Henley's work on his blog <a href="https://web.eecs.utk.edu/~azh/blog.html">here</a>. Recent pieces include: </p><ul><li><a href="http://web.eecs.utk.edu/~azh/blog/informationforaging.html">A theory of how developers seek information</a></li><li><a href="http://web.eecs.utk.edu/~azh/blog/allmyrejections.html">All my career rejections</a></li><li><a href="http://web.eecs.utk.edu/~azh/blog/coderibbon.html">Navigate your code like it's 2021</a> </li><li><a href="http://web.eecs.utk.edu/~azh/blog/yestercode.html">Why is it so hard to see code from 5 minutes ago?</a></li><li><a href="http://web.eecs.utk.edu/~azh/blog/inquisitivecodeeditor.html">An inquisitive code editor: Overcome bugs before you know you have them</a></li></ul><p>How much time does the average developer spend typing in their editor versus researching, exploring, and pondering? Henley believes half an hour of inputting actual code a day is realistic, despite what you've heard about the 10X developer in your area. </p>