Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

Xeee

Design or Implementation ??!!

This topic is 5748 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

which is more important/harder, Design or Implementation? i''m talking here about code-level design (classes/funtions and things like this) xee..

Share this post


Link to post
Share on other sites
Advertisement
Depends on the person I guess. Some people are very good at figuring out exactly what they want they want to do, and for the most part, how they need to do it. Other people are better at sorting through problems they run across and they still end up with very good work. I guess I would consider myself more towards the later, though over time I have become more able at figuring things out ahead of time.

Knowledge and wisdom, knowledge and wisdom.

Importance wise... it doesn''t do you much good to design something if you don''t have any way of implementing it and it doesn''t do you much good to implement something that is designed so poorly it is useless.

Colby

Share this post


Link to post
Share on other sites
Design is definitely imperative and even more so than implementation. A good design will save many hours of redesign during implementation. Design is more important than implementation because a design can be implmemented in any programming languages.

Both design and implementation come with experience.

Kuphryn

Share this post


Link to post
Share on other sites
Good design is crucial. You get to a point where the language doesn''t impede you anymore but you don''t know where to go with your design because you are inexperienced. That is me

Share this post


Link to post
Share on other sites
A good design helps determine the critical path of data structures and helps avoid a lot of recoding to accommodate missed designs that would not have been necessary had you generated a bullet-proof design doc beforehand.

However, that doesn''t necessarily make implementation easier, it just avoids a lot of mistakes. You might get the design doc done, and then set up all your data structures, scene graphs, optimization algorithms, etc. to accommodate the design and then say, "Holy MOLY this is complicated. I should have just made Tetris or something!"

Share this post


Link to post
Share on other sites
For me, design is a lot harder. In fact, once I''ve designed everything, implementation is almost trivial typing. But sometimes I run into problems when I just try to design everything and the amount of stuff to keep in mind keeps growing and growing.. Then it''s good to just start typing the code and see what it comes out. And refactor if it doesn''t look good.

Which one is more important? Well, with my coding style, design is almost everything there is, coding is just putting it down sometime later..

Share this post


Link to post
Share on other sites
Design is harder for me, once i have a good design i can code an implementation which i think is easier. i also end up changing designs a few times before i finish an implementation because the first few didn't work well.

[edited by - billybob on December 27, 2002 4:11:29 AM]

Share this post


Link to post
Share on other sites
I''m like everyone here, design is hard. If you get too far into design then implementation might throw you a monkey wrench while if you don''t do enough design you keep recoding stuff like mad It''s a ying-yang type thing, a balance.

Share this post


Link to post
Share on other sites
And before design and implementation, the most important thing is the answer to this question : "what exactly do you want to do ?", IOW a detailed specs. You can have the best design and implementation, if it does not fulfill the needs, it''s just a bullshit.

At my work, I was involved in some project where the needs of the customer was hardly specified (develop a publishing system, here are the forms, one or two rules of management, good luck !), and there was no time to get better specs because of marketing schedules (grrrrr).

Fortunately a significant part of my job was ok, but at most half of the work had to be redone after customer feedback -and mostly about the topics that have been specified- ("finally it should not be managed like this, I don''t like this form, etc...")

Now, back to Design and Implementation, a key element is experience with the tools you use. 5 years ago I wanted to write the best text editor in Java during my spare time, extensible, multilangage etc... And I was a newbie in Java. Finally I rewrote from scratch 3 times, because with my growing experience in Java and OOP I felt that my previous desgin was full of flaws, and I boiled down my requirements as well to what I really need (use UTF8 as native encoding).

I finally ended up with a working, bug-free text editor ! But now I also have the basis to develop within minutes the skeleton (GUI and programmatic interface) of a new app with standard fonctionnality and behaviour. What I could not do five years ago when I got the first version hardly working, with a bloated source.

----
David Sporn AKA Sporniket

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!