>>> Yah, plus your technical writing isn't bad either, from the few 
>>> snippets you've posted here when you write about things you enjoy.
>>
>> Ooo... really?
> 
> Really. You could write informal white-papers that other geeks would 
> read, methinks.  (At least, I read what you write and find it interesting.)

Heh. I've still failed to convert even one single person to Haskell yet. 
 >:-)

> The part others seem to think you lack is the knowledge of how to 
> structure a document that's bigger.  You need to be able to say (a) why 
> would the reader want to read this document, and (b) present it in an 
> order and form that makes it easiest to understand.

Yeah, I'm not too good at that. I know that you're supposed to say 
everything thrice and all that, I'm just not good at ordering my 
thoughts in a coherant way.

> Why  do you say you don't know how to write a report, when you're 
> getting praise for the quality of your report from people whose job is 
> to *judge the quality of your report*. :-)

It's not a report, it's a policy document. Different set of rules...

Post a reply to this message