4 ms·
Am I the only one who finds that diving in and exploring-through-doing is the best way to avoid thought-paralysis?
by locopati 16y ago
Am I the only one who finds that diving in and exploring-through-doing is the best way to avoid thought-paralysis?
- mhd 16y agoWhich is why you wait for a long time until you introduce types. (Assuming that the pun was intended)
- stcredzero 16y agoYes, you can dive in and explore-through-doing as a precursor to actually your actual coding. In good Smalltalk environments, the best way to read (and write) code is often in your debugger. This way, you add some empiricism to double check your reading comprehension. Doing iPhone development in XCode, I find it's best to try out code with lots of NSLog statements and a breakpoint in the new routine, so I can explore what's happening at runtime. (The NSLog statements are mainly to get around annoying quirks in the inspectors when you have really long Strings.) This is probably just my taking my Smalltalk habits and trying to do analogous things in XCode/Objective-C.