Code Design Methods

by **Labman** » Wed Dec 09, 2009 3:44 am

Lots of singleton use

I tried using pen and paper and it can be good for sketching out some new code, but I can quickly get out of date and is hard to bring up to date without recreating what you have done.

by **frag.machine** » Wed Dec 09, 2009 10:10 pm

by **lth** » Thu Dec 10, 2009 8:08 am

by **Wazat** » Fri Dec 11, 2009 3:34 am

by **frag.machine** » Sat Dec 12, 2009 2:46 pm

by **Wazat** » Sat Dec 12, 2009 5:26 pm

by **Labman** » Mon Dec 14, 2009 1:14 am

I totally agree with not doing UML etc for feature adding to already existing systems, esp if they don't have anything like that to start with as you would have to model a lot of code that already exists bogging you down.

I also agree that over planning isn't a good idea. Currently I'm only planning ahead for the current and next iteration of my project, if it's not planned for the next couple of iterations, its not a requirement yet. It's much easier to redesign code once you know exactly what it's going to do rather than planning a long way ahead. Unless you are doing comprehensive design, and who wants to do that in their spare time anyway?

by **Team Xlink** » Mon Dec 14, 2009 3:13 am

by **Wazat** » Mon Dec 14, 2009 3:44 am

by **Wazat** » Wed Dec 16, 2009 2:38 pm

I would just like to point out that tackles, and answers, this very issue.

by **Junrall** » Fri Jan 15, 2010 6:52 am

by **Teiman** » Fri Jan 15, 2010 8:41 am

Code Design Methods

Code Design Methods

Who is online