On Dec 20, 2007 1:30 AM, Uwe Grauer <[EMAIL PROTECTED]> wrote:
> Ed Leafe wrote:
> > 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.
> >
>
> This is so true.
Not always...
>
> > 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.
> >
>
> The above is more important as bigger the projects are.
> The most bigger projects fail because people tend to write code
> instead of thinking about the problems.
You can think about the problem without writing stuff down. Even if I
write it down, flowchart the code for every feature, etc., half the
time I still end up overhauling it anyway because it doesn't interface
nicely with a new feature. In the time that it takes for me to
actually write out everything, I could have a first prototype running.
Also, if you try to implement all the features of a big project all at
once, the code will be one big pile of spaghetti. I have never seen a
good software developer tackle a big project like that. It is always
a base implementation first, then start adding features...
Still, we have sparked a religious war here and I hope that this will
all get dropped so we can move on to more productive things. Code the
way that is most productive and natural for yourself. There is no
right or wrong way to develop code, just like there is no right or
wrong way to learn things.
Cheers,
Nate L.
_______________________________________________
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]
