title: Use of the term "page fault" not relating to virtual memory?
body: <p>In a number of situation, I've found my self using the term "page fault" to describe something other then virtual memory. For example:</p>
  
  <ul>
  <li>When manually refactoring a block of code into a function, I "page fault" the variable I need into the argument list, that is I start with a void list and add whatever the compiler tells me is missing until things compile.</li>
  <li>When working with a new system I generally take guesses at how it works and only "page fault" knowledge from the docs when my first one or two guesses don't work.</li>
  </ul>
  
  <p>Is this (mis)use of the term to describe error driven advancement common? </p>