As a fresh Computer Science graduate this is exactly what I needed to hear. It's cool to know about OOP, Functional Programming, Monads and how to write parsers etc. But... at the end of the day it's whether or not these tools are relevant to the problem you are trying to solve, if they're not then they are a distraction and will make the problem you are trying to solve worse. Hint, most of the time they are not relevant or are loosely applicable. Simplest and most direct solution is king until proven otherwise.
What you say in general doesn't make sense. You say that this was what you needed to hear and you are a fresh graduate, but then you give advice to people. Are you inexperienced, or experienced? You can't be both. That aside, your argument is too vague. What "simplest and most direct solution" means? Like, does that include using electron and phaserjs for building your game, becuase that's one of the simplest things you can do. Or using something simplistic, like c, for it? Thinking about how you are going to do your architecture isn't related to OOP, FP, Monads or how to write parsers. Architecture depends on needs of your games, which is closely related to hardware you want to support. Every wasted cycle is a waste; and being a good engineer is deciding whether that waste was worth it or not. So, it is your responsibility to find good solutions to the problems you are solving; which doesn't really correlate with "simplest and most direct solution is king until proven otherwise". Yes, profiling is part of the craft; but programming isn't magic; you still need to think about your data access patterns and decide if they are worth it or not.
I needed to hear this.
As a fresh Computer Science graduate this is exactly what I needed to hear. It's cool to know about OOP, Functional Programming, Monads and how to write parsers etc. But... at the end of the day it's whether or not these tools are relevant to the problem you are trying to solve, if they're not then they are a distraction and will make the problem you are trying to solve worse. Hint, most of the time they are not relevant or are loosely applicable. Simplest and most direct solution is king until proven otherwise.
What you say in general doesn't make sense. You say that this was what you needed to hear and you are a fresh graduate, but then you give advice to people. Are you inexperienced, or experienced? You can't be both.
That aside, your argument is too vague. What "simplest and most direct solution" means? Like, does that include using electron and phaserjs for building your game, becuase that's one of the simplest things you can do. Or using something simplistic, like c, for it? Thinking about how you are going to do your architecture isn't related to OOP, FP, Monads or how to write parsers. Architecture depends on needs of your games, which is closely related to hardware you want to support. Every wasted cycle is a waste; and being a good engineer is deciding whether that waste was worth it or not. So, it is your responsibility to find good solutions to the problems you are solving; which doesn't really correlate with "simplest and most direct solution is king until proven otherwise". Yes, profiling is part of the craft; but programming isn't magic; you still need to think about your data access patterns and decide if they are worth it or not.
Good advice 👍
very sound advice
why is the audio fked?
make a game with no entities -- problem solved
"keep it real" - worst advice ever
Pfffttt
Just use classes to make entities