To me, a big part of multiplying your programming efficiency isn't about a crazy investment of time or ruining your other priorities in life, it's more about ob

To me, a big part of multiplying your programming efficiency isn't about a crazy investment of time or ruining your other priorities in life, it's more about objectively looking at how you work and removing or minimizing the things that are a waste of time. It's really about self reflection. Are you spending a lot of time hunting and pecking through menus? Why not learn the keyboard shortcuts? Are you confused about part of your tech stack, maybe the build system? It might be worth a couple hours to get a solid foundation rather than leaving it as a mystery box. There are huge improvements in time saved from cleaning up a lot of little things. The other thing, I think, comes down to losing your religion. For instance, people tend to treat SOLID religiously. I won't claim whether those principles are right or wrong, but what I don't see a lot of programmers do is consider why they believe those things (a blog told them to do it?), and whether those concepts fit into what they're currently doing. Is dependency injection actually simplifying your life? I'm not saying it's a bad idea, I just think a lot of programmers cargo cult things without considering the context they were invented in. The most efficient coders I know rarely over-architect things.