Post

I hate hearing the word ‘framework’ from any engineer. You can replace that word with ‘overengineer’ and you'll be right about 90% of the time. You don't have to make frameworks for everything! Stop making everything 'robust' and 'future proof' while the project is still being iterated.

Like building a framework so that players can fire off 5 abilities at the same time, and the game designers are still iterating what the gameplay will even look like! How much time are you wasting? Or making an entire animation system for feet on staircases: Will the game even have many staircases?

Instead, build an initial version of something, with throwaway code, see if it's any good with users, adjust it, do that a few times, and then when users are happy, and you think it'll be used many times in many places, you make a framework for re-use. But not any moment sooner!

This implies that companies generally have management that understands the importance of throwing away prototypes to make 'the real thing'. "But we can see the pixels on screen doing the thing we want; why throw it away? Just iterate on that and ship it!"