Started doing exactly that a few years back when my own project was getting out of hand. I literally made a new folder called “core” and moved over the 10 or so functions that got called every single day, then shoved everything else into a “vault” folder no new dev even needed to peek at unless they got curious. Ended up trimming about 40% of the codebase once I actually looked at usage stats and saw stuff I wrote drunk at 2am never got touched. Made a mental note to kill any feature that didn't hit 5% usage over a couple months, and onboarding went from a two day nightmare to a quick afternoon chat.

Exactly, it's the difference between fixing it once and fixing it every single time. Auto layout turns spacing into a rule instead of a guess. Once you set it, you can forget it.

Guess you've never had to scrape off half a deck cause you torched it too hot and turned it into a charcoal grill. Faster doesn't always mean better when you're fixing your own mistakes later. But hey, you do you, I'll stick with my stripper and a scraper while I sip my coffee.

You said people come in Monday knowing exactly what to do first. That's the whole thing, isn't it? We treat Monday like a fresh start, but we send people in blind. It's like the difference between showing up to build a shed with a plan versus just a pile of wood. Your Friday meeting gives them the plan. Why do we act surprised when mornings are wasted on figuring stuff out?

Ever think about what that screw is doing to the wood fibers when you drive and then back it out? You're basically drilling a hole twice. On wet or engineered lumber, that could leave a weak spot that splits later when you nail near it.