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.

This is one of the two all-time tradeoffs in engineering: Doing something big now to POTENTIALLY save later, or doing it quick now. With the other one being flexibility vs simplicity.

YAGNI vs. YMGNI

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!"

The exception is if you're using an engine or API that has an existing framework, such as GAS in Unreal. Please use that framework, and do not try to reinvent it! Make it do the work for you, and stick to it from the start, as it will be intertwined in all the other already existing systems.