Page 1 of 1
Technical Design
Posted: Thu Jan 22, 2009 6:58 am
by LuciDreamTheater
How do you design your programs and games?
Do you jump in without preparation, or are you more sophisticated in your approach? I've started to see the value in design, but I don't know exactly how to do it well. Sometimes I write flowcharts or "clouds," while other times I just write a short list of what needs to be done, but this seems insufficient. A case in point is with the side scroller I'm making. I wrote the level loader, but then realized I need to expand it to include layers and the walkability of each tile. It's not a big setback, but it would have been nice to have prepared for this ahead of time or at least to have had it done when I wrote the loader in the first place.
What can I do, specifically, to improve my designs?
Re: Technical Design
Posted: Thu Jan 22, 2009 8:39 am
by MarauderIIC
For a quick reply: class/UML diagrams are a great way to go. A requirements listing is good too. But the thing with design is that no matter what approach(es) you take, you have to do it well.
Perhaps a more in-depth reply later.
Re: Technical Design
Posted: Thu Jan 22, 2009 8:41 am
by programmerinprogress
My first major(ish) project I decided to do, BLOCK started off a little strange really.
I had been learning how to use SDL about a year back, so I wanted to start a project. In the beginning it was just an experiment, so I didn't start with any design notes, but as I continued adding functionality, I started to document all the new features I was adding, however this approach became cumbersome, and I basically had a half-documented solution, and adding minor updates to the functionality became difficult.
Therefore I'm going to suggest you do a little pre-project planning before you start the project.
Consider maintainability and expandability, Since you will likely need to re-use your code for other purposes, or expand your current project in the future.
In a nutshell, I would do some planning(and i'm not just being hypothetical, I intend to do extensive planning for my next project).
Re: Technical Design
Posted: Thu Jan 22, 2009 1:01 pm
by Chaos Clown
I don't tend to plan anything. Usually, I just get an idea, then code it almost straight away. I wouldn't recommend this approach though. You end up with REALLY messy, inefficient code and/or a craptonne of rewrites. But, hey, I'm still learning, there's time to change
Maybe I need a MarauderIIC to fix up my code!
Re: Technical Design
Posted: Thu Jan 22, 2009 9:50 pm
by Arce
Maybe I need a MarauderIIC to fix up my code!
Don't we all!
Re: Technical Design
Posted: Fri Jan 23, 2009 9:23 pm
by eatcomics
Chaos Clown wrote:I don't tend to plan anything. Usually, I just get an idea, then code it almost straight away. I wouldn't recommend this approach though. You end up with REALLY messy, inefficient code and/or a craptonne of rewrites. But, hey, I'm still learning, there's time to change
Maybe I need a MarauderIIC to fix up my code!
We should invent a pocket marauder, so everyone can have overly edited posts, and everyone would have the best grammar possible