Seeing you tell Prime that if the Tower structure just has the animation variables inside, the code would be by a multiple strictly better in all senses really made me feel the damage the current best practices did to my brain by not being nuanced. Not wanting to start watching 1000h+ of Handmade Hero, I'm curious if someone has something like a list of "good practices", that programmers/college graduates can't even start thinking to question, with some real alternatives to start understanging the "tradeoffs" made by default.
Very good case study with the health bar that would definitely benefit almost all the programmers working on new code I would definitely clip and tweet.
Maybe I am very biased on this because you literally decribed what I had to do to my animation system, and my conclusion back then was that animation systems are just difficult because of those things everybody has to do.
This was a great talk. I would love to hear you talk more about properly executing the prototyping phase for the more complicated type of game. If the concept is something like a modern RPG game with towns, npcs, action combat, questing, and monsters, where do you draw the line and decide you've made enough of a prototype and can confidently switch into performance architecture work?
Unfortunately I think that is more of a question for a game designer, because I am not really qualified to assess the state of game designs. What I can say is that project-management wise, you need to make sure you have made your architectural changes for performance _before_ you spin up any content creation that will lock in that architecture. Once people have made a significant amount of content that depends on particular architecture choices, it becomes very difficult to change. That is what you need to watch out for.
Saw this on youtube before: so helpful. As someone coming from an academic background, who's been looking to really elevate their skills writing software (vs just translating math into something that a computer can execute given arbitrary time) getting this sort of real-life informed thinking from someone who values the engineering of software engineering as well as the 'what make a real project work' feels remarkably difficult. Thanks for this.
Seeing you tell Prime that if the Tower structure just has the animation variables inside, the code would be by a multiple strictly better in all senses really made me feel the damage the current best practices did to my brain by not being nuanced. Not wanting to start watching 1000h+ of Handmade Hero, I'm curious if someone has something like a list of "good practices", that programmers/college graduates can't even start thinking to question, with some real alternatives to start understanging the "tradeoffs" made by default.
Very good case study with the health bar that would definitely benefit almost all the programmers working on new code I would definitely clip and tweet.
Maybe I am very biased on this because you literally decribed what I had to do to my animation system, and my conclusion back then was that animation systems are just difficult because of those things everybody has to do.
This was a great talk. I would love to hear you talk more about properly executing the prototyping phase for the more complicated type of game. If the concept is something like a modern RPG game with towns, npcs, action combat, questing, and monsters, where do you draw the line and decide you've made enough of a prototype and can confidently switch into performance architecture work?
Unfortunately I think that is more of a question for a game designer, because I am not really qualified to assess the state of game designs. What I can say is that project-management wise, you need to make sure you have made your architectural changes for performance _before_ you spin up any content creation that will lock in that architecture. Once people have made a significant amount of content that depends on particular architecture choices, it becomes very difficult to change. That is what you need to watch out for.
- Casey
Your expression when he showed you that vtable stuff was priceless )
Saw this on youtube before: so helpful. As someone coming from an academic background, who's been looking to really elevate their skills writing software (vs just translating math into something that a computer can execute given arbitrary time) getting this sort of real-life informed thinking from someone who values the engineering of software engineering as well as the 'what make a real project work' feels remarkably difficult. Thanks for this.
It was great, looking forward to more.