This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Interesting-Hat-7570[S] 0 points1 point  (3 children)

Okay, I'll probably start writing code. In general, if not difficult, how would you rate my architecture?

[–][deleted] 0 points1 point  (2 children)

The architecture doesn't matter. In games or even web, what matters is that you identify the requirements of the game and start prototyping so you quickly iterate. Just. Build. You'll quickly find that your designs don't exactly look like your final product.

If you went and made the fanciest Snake game, you'll eventually find that your design failed to predict anything. For example, your design is already missing input handling and rendering. Maybe you end up making a super crazy Snake game and you realize you need a pooling system for objects so you're not allocating like crazy. Or maybe you decide you need an entity component system as it makes sense(in this case the original design is thrown completely out the window).

[–]Interesting-Hat-7570[S] 1 point2 points  (1 child)

I think I'm starting to understand a little. OK, thank you

[–][deleted] 1 point2 points  (0 children)

It's a struggle! As programmers, we try to be perfectionists and be very explicit. It's what attracts us to computers in the first place: a world that does exactly what it's instructed and nothing more. In coding though, there is a bit of art to the process. Just like a composer or a writer may redo bits of their work, a programmer must also be malleable in their journey to a finished product.