[racket-dev] RFC: Coding Guidelines

I am fine with these changes. 

On Aug 19, 2010, at 10:53 AM, Jay McCarthy wrote:

> I hope I've incorporated much of the feedback from this thread:
> 
> http://faculty.cs.byu.edu/~jay/tmp/201008161509-guidelines.html
> 
> Jay
> 
> On Thu, Aug 19, 2010 at 8:14 AM, Matthias Felleisen
> <matthias at ccs.neu.edu> wrote:
>> 
>> Yes. I started using the phrase "I have bug reports, therefore I exist" at Rice. I think Jay should add this phrase right next to the other quote.
>> 
>> 
>> 
>> 
>> On Aug 19, 2010, at 10:03 AM, Robby Findler wrote:
>> 
>>> Guys: we need one more thing to go into the beginning of these
>>> guidelines. Specifically, we should say (something like) "Bugs are
>>> something to be proud of; not to be ashamed of." the rationale being
>>> that there are always bugs, but if they are unknown bugs then it means
>>> your software is not being used.
>>> 
>>>  It is the way we choose to fight our bugs that determines our
>>> character, not their presence or absence.
>>> 
>>> Robby
>> 
>> _________________________________________________
>>  For list-related administrative tasks:
>>  http://lists.racket-lang.org/listinfo/dev
>> 
> 
> 
> 
> -- 
> Jay McCarthy <jay at cs.byu.edu>
> Assistant Professor / Brigham Young University
> http://teammccarthy.org/jay
> 
> "The glory of God is Intelligence" - D&C 93