On Dec 19, 2007, at 7:33 PM, Nate Lowrie wrote:
>> Make it work, then make it right. Then, make it fast, but that's a
>> different topic altogether.
>
> I second that notion...If you would look over my shoulder as I code an
> app, I code it rather horribly the first time. It is generally
> implementation specific, not refactored, very ugly code. But then
> after you get it working you go back and you refactor it. Optimizing
> ("making it fast") is just another refactor, but it shouldn't be done
> at the expense of clean code...
My guiding principle is that the sooner you start writing code, the
longer it will take to finish.
I tend to play with ideas with a pen and paper, trying to imagine
the flow necessary for the problem. By doing this first, the general
approach will be clear long before I start writing any code. This
limits the amount of time necessary for a re-write, since it's
usually designed correctly the first time I actually write it.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
