I tend to write a lot of pseudocode and create block diagrams on a whiteboard first before I touch the keyboard. I've found this reduces debugging time and helps me plan the architecture of the app better. Once I start writing code statements, the details of the language and object structure tend to distract me.
John --- David Jackson <[EMAIL PROTECTED]> wrote: > I can understand that, but I, myself, don't seperate > the design from the > implementation. Mostly because I do both > interchangeably (I design some > rough form, and then implement it, and then design > more as I go along). > However, I probably spend more time debugging and > enhancing (hacking) > than I do designing and implementing. > > David > > John Hebert wrote: > > >--- David Jackson <[EMAIL PROTECTED]> wrote: > > > > > >I see your point, but I separate the design of an > >application from the actual creation of code > >statements. In my opinion, the design is the most > >important phase of software development. I think > that > >is what Edmund was referring to. > > > >A good book to read about this very topic is > "Software > >Project Survival Guide" by Steve McConnell > >(http://www.stevemcconnell.com). Heck, all the > books > >he's written are great. > > > >John > > > > > > > >__________________________________ > >Do you Yahoo!? > >The all-new My Yahoo! - What will yours do? > >http://my.yahoo.com > > > >_______________________________________________ > >General mailing list > >[email protected] > >http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
