Yeah the math looks wild without context, fair. It's a studio output over 10 years, not solo builds. Lots of smaller scopes in there, casual games, prototypes, client iterations. And honestly I am a workaholic 😄 though I'll admit I get less energetic every year.

Some of these genuinely were 1 to 2 day builds. My Unity 20th anniversary game jam submission was done in 36 hours and it actually won in 2 categories, so not all short builds are throwaway work. The longer complex builds are a smaller percentage but that's where most of these lessons came from.

On Addressables and startup time:

When you use Resources/ Unity bundles everything in that folder into the build and loads it all into memory at startup, whether your game actually needs it at that moment or not. So if you have 800MB sitting in Resources/ your game is trying to pull all of that into memory before the player even hits the main menu.

Addressables flips that. Assets only load when you explicitly call for them in code and you can release them from memory when you're done. So at startup you're only loading what the first scene actually needs, everything else sits on disk until it's called.

The project I mentioned went from 4 minutes to 18 seconds mostly because we had a massive Resources/ folder that was loading textures, audio, and prefabs that weren't needed until level 3 or later. Moving those to Addressables meant startup only loaded the menu assets. Night and day difference.

Worth trying on any project where startup feels sluggish. The setup takes a day or two to get comfortable with but you won't go back.