|
|
|
| P is for Practical | |
| PerlMonks |
Re: Coming up with code designby holygrail (Scribe) |
| on Jun 23, 2001 at 17:39 UTC ( [id://90980]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
It depends on the program that I need to write: With small programs, or things that are quite obvious, I just start coding bit-by-bit. Testing each step, modifying, and letting the program grow... However, when I work on large projects I want a decent design. Either made by me, or by some software architect. I don't just start programming. I've seen it too much before: start working and half way you come to the conclusion that the design was bad and that important and you can start al over again. No thanks. Even that piece of paper and pen of you won't be enough for large projects. Every part of the project has to be thought about before you start coding. --HolyGrail
In Section
Meditations
|
|
||||||||||||||||||||||||