>> The word "explain" is semantically the same as "document" to most
>> people but not to the programmer community.
>>
>
>FWIW, I think the situation is closer to precisely the opposite. If I ask
>you to document what you do today, what will you do? Hold on to your
>receipts? Log mileage in your car? Compare being asked to explain what you
>do today.
Precisely my point (unless I miss your point). If I ask you to document
your trip you'll hand me receipts. If I ask you to explain your trip you
need to tell me why you went, what you did, and why I care.
Current documentation tools and standards attach an explanation to the
trip receipt ("I ate here"). What we need to keep a program alive is the
explanation of why you did it, what you did (the inline code), and why I
care.
Tim Daly
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
