Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: Re: My number 1 tip for developers.

by htoug (Deacon)
on Sep 12, 2003 at 07:14 UTC ( [id://290945] : note . print w/replies, xml ) Need Help??

in reply to Re: My number 1 tip for developers.
in thread My number 1 tip for developers.

That was the preferred way of doing things when I started - way back in the early '70ies.

Things have progressed since then!

The recommended way is now a variant of Test early, test often mixed with Iterate - either XP, Agile or perhaps some form of RUP (for the BSDM fans) or whatever the current name is.

Nowadays you prototype, testing as you go along, releasing incrementally and refactoring when needed, all in an iterative way. All this requires a strong test-suite, which is buld preferebly before development. Testing is a lifelong process, and the testsuite keeps growing - often it is larger than the application - but it keeps everyone happy, as we all know that the system is working as expected.

  • Comment on Re: Re: My number 1 tip for developers.

Replies are listed 'Best First'.
Re: Re: Re: My number 1 tip for developers.
by Anonymous Monk on Sep 13, 2003 at 09:36 UTC
    That's why I say test and verify - you can do this while implementing .

    Basically I agree with this other AM at Re: Re: Re: My number 1 tip for developers..

    You and BrowserUk both seem to have a different understanding of the steps. Perhaps I should have emphasized basic in the basic software engineering steps. There are no subcategories. There are no metrics.

    BrowserUk says The whole point of the tip is the idea that you learn to recognise (as early as possible) when you are wasting time trying to 'get something to go', and that's a good tip if you get writers coders block. I suppose my only uneasiness with BrowserUks original node is that he first tips on the mechanics of banging a keyboard, when spec/analysis and then design is what you always need to start with.