when programming games Thread

Hello,
Just a question to programmers here.
Do you design UML diagrams before actually coding a game? Like do you structure the code and plan the design like following proper software engineering methodologies or do you just code as you go along? I ask this because i took some software engineering classes and they always emphasis designing the architecture before coding.

It depends on the project and the setting. If I'm working with a team of programmers on the same project (like at my job), then yes, we typically design stuff via some kind of diagram before diving into it. The purpose of this is so that you can all work on the same thing w/o stepping on eachothers toes.

However, if I'm tasked with something to complete by myself, or if I'm just doing something on my own from home, I usually take a hybrid approach. I do w/e research I need to, then start coding, but not like normal. I write out the skeleton of the project (classes, functions, etc) but w/o doing any actual implementation. I name the classes and functions according to what I intend them to do, then leave them empty. The benefit of this is that you get the project mapped out, making w/e design changes you need as you go, but w/o needing to put a lot of time into implementation. Once everything is arranged like this, its easier to see design improvements that you can make, and since its just skeleton code, the changes are typically pretty easy.

Let me know if any of this didnt make sense.

Edited by: lancer611

alright thanks man, yeah everything made sense

for the engine/framework I do informal design. More like a flowchart rather than a actual UML compliant diagram.

For the game no way. Games are too experimental to be able to predict their overall layout. I typically do rapid prototyping the look at what did and didn't work. After I"m confident I take what some might consider a aglie approach to development but really it's just making sure that you dont have a major iteration that is broken or not architecturally sound.

The thing about software engineering and post-secondary is the teacher will typically explain something as if it's a postulate wen in reality the need and use of different techniques is highly dependent on the type of project you are doing.

yeah okay thanks for the info you guys.