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.
Be sure your code is the best, and hpaste it, before looking at this.
My solutions are here:
http://hpaste.org/40600/project_euler_1
The hpaste has information about running criterion benchmarks.
Less elegant, but direct.
http://hpaste.org/40609/more_like
Ayyo, anybody else going to give this a try? Should we start talking
about the solutions?
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:
On Wed, Oct 20, 2010 at 9:24 AM, Francesco Lazzarino