<p>Here are a few tips that can make it easier to find and fix problems in Nu programs.</p>
<ul>
<li>First, it's a good idea when working with any dynamic language to write in small bits and test frequently. </li>
<li>Use the embedded console to explore and interact with objects. You can also use it to reload code into a running application. This allows you to build and test your code incrementally.</li>
<li>Use <strong>nush</strong> from the terminal to explore.</li>
<li>Debug crashes with <strong>gdb</strong>. From the gdb console, you can say things like <nobr><code>po [object stringValue]</code></nobr> to see a string representation of a Nu object. You can use that to see the Nu code that is being evaluated. You can also send other Objective-C messages from within gdb. For example, to see the contents of an NSDictionary, use <nobr><code>po [dictionary description]</code></nobr>.</li>