From: James Edward Gray II <james@...>
Date: 2006-07-03T23:53:17+09:00
Subject: Re: [QUIZ] Sending Ruby code vs. provding URLs

On Jul 3, 2006, at 9:43 AM, Dave Burt wrote:

> There are also the problems of
> in-line code being re-formatted by mail agents; this is avoided by  
> using
> attachments rather than in-line code.

This generally isn't much of a problem if you keep your lines short,  
which I believe is a good habit to get into anyway.  I do try to  
correct poorly wrapped lines when I pull the code out.

> I always try and write the key features of my code, or why I think
> people would want to read it, kind of like an executive summary (but
> not). I like when people do this (with library announcements or  
> whatever
> else, too) because it not only helps the reader decide whether it's
> worth their time, but it also provides a "way in" to the code if  
> they do
> decide to look into it.

I love it when solvers do this, because it serves as the cliff-notes  
for me when I am rescanning the solutions to write the summary, "Oh  
yeah, I wanted to talk about that..."

James Edward Gray II