robwelan · June 17, 2020 20:56
diff --git a/article-table03-building-and-using-a-table-of-queries b/article-table03-building-and-using-a-table-of-queries
 <table style="width:90%" border="1" cellPadding="8" align="center">
   <tbody>
      <tr>
         <td>
            <aside>NOTE: You may have noticed that I include both a prefix and a suffix on my variable names, plus suffixes on functions that I write (where feasible). This is because I like my code to be readable and function in a strict sense. If I declare a variable with data type Long, but I put a $ suffix on it within the code (because I forgot, OK?), I&#x27;d like to be able to be warned of my mistake before I check with the debugger. The &quot;lng&quot; and &quot;str&quot; prefixes help prevent these sorts of blunders in my code. I feel that this forethought reduces the time required to get through functional testing. A lot of the simple bugs that one can create are eliminated by abiding by strict naming conventions.</aside>
         </td>
      </tr>
   </tbody>
 </table>
	<table style="width:90%" border="1" cellPadding="8" align="center">
	<tbody>
	<tr>
	<td>
	<aside>NOTE: You may have noticed that I include both a prefix and a suffix on my variable names, plus suffixes on functions that I write (where feasible). This is because I like my code to be readable and function in a strict sense. If I declare a variable with data type Long, but I put a $ suffix on it within the code (because I forgot, OK?), I'd like to be able to be warned of my mistake before I check with the debugger. The "lng" and "str" prefixes help prevent these sorts of blunders in my code. I feel that this forethought reduces the time required to get through functional testing. A lot of the simple bugs that one can create are eliminated by abiding by strict naming conventions.</aside>
	</td>
	</tr>
	</tbody>
	</table>