>> My way of looking at a text or presentation: Look at it as if it is a 
>> program. The conclusions are the main routine. The lines in the 
>> conclusions call various subroutines (aka the previous sections and 
>> slides) that can in turn call other subroutines (paragraphs). You 
>> should therefore be able to draw a flowchart of the concepts in your 
>> text. A text is good if 1) no external subroutines are called (i.e. 
>> everything is defined within the text or common knowledge to the 
>> audience) 2) there are no dead branches. 3) all subroutines are define 
>> before use or explicitly declared as something to fill in later.
>> When I said that a programmer should be able to write a decent report 
>> (or give a good presentation for that matter) because the skills 
>> required are the same, the above is what I meant.
> 
> My God... this is genius. Genius, I say! 0_0
> 
> I have never, ever thought about writing stuff that way... Damn, so 
> *this* is what being intelligent must feel like? Heh. I gotta try 
> writing something now...

And Darren's suggestions about making an outline first match the analogy 
too (you should design your code structure before actually filling in 
actual code inside functions / methods).

Post a reply to this message