Just to get stuff going on, let's do Project Euler #1.
Whenever we code, please make your solutions as perfect as they can be. Realize what choices you're making, and have reasons for your decisions. After you think you've made every byte as good as you know how to make it, put it on hpaste. Then we can talk strategy, style, naming, efficiency, etc.
On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: > Just to get stuff going on, let's do Project Euler #1.
> Whenever we code, please make your solutions as perfect as they can be. > Realize what choices you're making, and have reasons for your decisions. > After you think you've made every byte as good as you know how to make > it, put it on hpaste. Then we can talk strategy, style, naming, > efficiency, etc.
On Fri, Oct 15, 2010 at 1:39 PM, Ian Taylor <ibtay...@gmail.com> wrote: > I read Johan Tibell's cufp presentation and thought I'd apply some of that here. > http://github.com/tibbe/cufp-2010
> The hpaste has information about running criterion benchmarks.
> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >> Just to get stuff going on, let's do Project Euler #1.
>> Whenever we code, please make your solutions as perfect as they can be. >> Realize what choices you're making, and have reasons for your decisions. >> After you think you've made every byte as good as you know how to make >> it, put it on hpaste. Then we can talk strategy, style, naming, >> efficiency, etc.
sorry guys i'll try, i've been really busy all day and all other work days. i'm giving it a try after lunch
On Mon, Oct 18, 2010 at 11:44 AM, Brian Lewis <br...@lorf.org> wrote: > Ayyo, anybody else going to give this a try? Should we start talking > about the solutions?
On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: > Just to get stuff going on, let's do Project Euler #1.
> Whenever we code, please make your solutions as perfect as they can be. > Realize what choices you're making, and have reasons for your decisions. > After you think you've made every byte as good as you know how to make > it, put it on hpaste. Then we can talk strategy, style, naming, > efficiency, etc.
> I could only spend a little time on this one. Sorry!
> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: > > Just to get stuff going on, let's do Project Euler #1.
> > Whenever we code, please make your solutions as perfect as they can be. > > Realize what choices you're making, and have reasons for your decisions. > > After you think you've made every byte as good as you know how to make > > it, put it on hpaste. Then we can talk strategy, style, naming, > > efficiency, etc.
>> I could only spend a little time on this one. Sorry!
>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >> > Just to get stuff going on, let's do Project Euler #1.
>> > Whenever we code, please make your solutions as perfect as they can be. >> > Realize what choices you're making, and have reasons for your decisions. >> > After you think you've made every byte as good as you know how to make >> > it, put it on hpaste. Then we can talk strategy, style, naming, >> > efficiency, etc.
>>> I could only spend a little time on this one. Sorry!
>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >>> > Just to get stuff going on, let's do Project Euler #1.
>>> > Whenever we code, please make your solutions as perfect as they can be. >>> > Realize what choices you're making, and have reasons for your >>> decisions. >>> > After you think you've made every byte as good as you know how to make >>> > it, put it on hpaste. Then we can talk strategy, style, naming, >>> > efficiency, etc.
>>>> I could only spend a little time on this one. Sorry!
>>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >>>> > Just to get stuff going on, let's do Project Euler #1.
>>>> > Whenever we code, please make your solutions as perfect as they can >>>> > be. >>>> > Realize what choices you're making, and have reasons for your >>>> > decisions. >>>> > After you think you've made every byte as good as you know how to make >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, >>>> > efficiency, etc.
> >>>> I could only spend a little time on this one. Sorry!
> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: > >>>> > Just to get stuff going on, let's do Project Euler #1.
> >>>> > Whenever we code, please make your solutions as perfect as they can > >>>> > be. > >>>> > Realize what choices you're making, and have reasons for your > >>>> > decisions. > >>>> > After you think you've made every byte as good as you know how to > make > >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, > >>>> > efficiency, etc.
>> >>>> I could only spend a little time on this one. Sorry!
>> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >> >>>> > Just to get stuff going on, let's do Project Euler #1.
>> >>>> > Whenever we code, please make your solutions as perfect as they can >> >>>> > be. >> >>>> > Realize what choices you're making, and have reasons for your >> >>>> > decisions. >> >>>> > After you think you've made every byte as good as you know how to >> make >> >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, >> >>>> > efficiency, etc.
>>> >>>> I could only spend a little time on this one. Sorry!
>>> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> >>> wrote: >>> >>>> > Just to get stuff going on, let's do Project Euler #1.
>>> >>>> > Whenever we code, please make your solutions as perfect as they >>> can >>> >>>> > be. >>> >>>> > Realize what choices you're making, and have reasons for your >>> >>>> > decisions. >>> >>>> > After you think you've made every byte as good as you know how to >>> make >>> >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, >>> >>>> > efficiency, etc.
>>> >>>> I could only spend a little time on this one. Sorry!
>>> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> wrote: >>> >>>> > Just to get stuff going on, let's do Project Euler #1.
>>> >>>> > Whenever we code, please make your solutions as perfect as they >>> >>>> > can >>> >>>> > be. >>> >>>> > Realize what choices you're making, and have reasons for your >>> >>>> > decisions. >>> >>>> > After you think you've made every byte as good as you know how to >>> >>>> > make >>> >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, >>> >>>> > efficiency, etc.
On Wed, Oct 20, 2010 at 4:05 PM, Ian Taylor <ibtay...@gmail.com> wrote: > Your #3 has problems for small n. > ***Exception: Prelude.maximum: empty list
> On Wed, Oct 20, 2010 at 9:24 AM, Francesco Lazzarino > <flazzar...@gmail.com> wrote: > > #3 http://gist.github.com/636387 > > it took me a while to get my algorithm down to a reasonable runtime.
> > On Tue, Oct 19, 2010 at 2:39 PM, Francesco Lazzarino < > flazzar...@gmail.com> > > wrote:
> >> wow, bad-ass
> >> On Tue, Oct 19, 2010 at 2:37 PM, Christian von Kleist > >> <cvonkle...@gmail.com> wrote:
> >>> While working on #2, I saw this in the output of my fib function.
> >>> On Tue, Oct 19, 2010 at 2:03 PM, Francesco Lazzarino > >>> <flazzar...@gmail.com> wrote: > >>> > #2 http://gist.github.com/634687
> >>> > On Tue, Oct 19, 2010 at 8:55 AM, Francesco Lazzarino > >>> > <flazzar...@gmail.com> > >>> > wrote:
> >>> >>>> I could only spend a little time on this one. Sorry!
> >>> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> > wrote: > >>> >>>> > Just to get stuff going on, let's do Project Euler #1.
> >>> >>>> > Whenever we code, please make your solutions as perfect as they > >>> >>>> > can > >>> >>>> > be. > >>> >>>> > Realize what choices you're making, and have reasons for your > >>> >>>> > decisions. > >>> >>>> > After you think you've made every byte as good as you know how > to > >>> >>>> > make > >>> >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, > >>> >>>> > efficiency, etc.
On Wed, Oct 20, 2010 at 4:05 PM, Ian Taylor <ibtay...@gmail.com> wrote: > Your #3 has problems for small n. > ***Exception: Prelude.maximum: empty list
> On Wed, Oct 20, 2010 at 9:24 AM, Francesco Lazzarino > <flazzar...@gmail.com> wrote: > > #3 http://gist.github.com/636387 > > it took me a while to get my algorithm down to a reasonable runtime.
> > On Tue, Oct 19, 2010 at 2:39 PM, Francesco Lazzarino < > flazzar...@gmail.com> > > wrote:
> >> wow, bad-ass
> >> On Tue, Oct 19, 2010 at 2:37 PM, Christian von Kleist > >> <cvonkle...@gmail.com> wrote:
> >>> While working on #2, I saw this in the output of my fib function.
> >>> On Tue, Oct 19, 2010 at 2:03 PM, Francesco Lazzarino > >>> <flazzar...@gmail.com> wrote: > >>> > #2 http://gist.github.com/634687
> >>> > On Tue, Oct 19, 2010 at 8:55 AM, Francesco Lazzarino > >>> > <flazzar...@gmail.com> > >>> > wrote:
> >>> >>>> I could only spend a little time on this one. Sorry!
> >>> >>>> On Thu, Oct 14, 2010 at 5:48 PM, Brian Lewis <br...@lorf.org> > wrote: > >>> >>>> > Just to get stuff going on, let's do Project Euler #1.
> >>> >>>> > Whenever we code, please make your solutions as perfect as they > >>> >>>> > can > >>> >>>> > be. > >>> >>>> > Realize what choices you're making, and have reasons for your > >>> >>>> > decisions. > >>> >>>> > After you think you've made every byte as good as you know how > to > >>> >>>> > make > >>> >>>> > it, put it on hpaste. Then we can talk strategy, style, naming, > >>> >>>> > efficiency, etc.
