The Art Of Software Development (part 3): Coding To A Plan (Page 1 of 7 )
In the first two parts of this article, I spent lots of time and bandwidth spouting off about requirements, design, and the various types of documents you should develop prior to actually beginning implementation of a software project. If you're the kind of developer who hates documentation (is there really any other kind?), you've probably been wishing I'd just shut up and get to the point...or, in this case, the code.
Well, your wishes are about to be answered.
In this third part, I'll be focusing exclusively on the implementation phase of a software project, suggesting some general techniques and approaches that might come in handy when you finally sit down to write your application. The ideas discussed in the following pages are not new - heck, they're not even exhaustive - but they should nevertheless help you deliver cleaner, faster and more maintainable code.
Next: The Name Game >>
More Practices Articles
More By Vikram Vaswani, (c) Melonfire
/ 5 
