You'll reach the level you want to avoid doing all this.
What if future you has reached that level and people on your team are shipping spaghetti?
I feel like just emulating what you see in your first few jobs is ideal. (As in, ask coworkers who know the thing you’re working on) It could be great code to be inspired from, or mediocre. Either way you get some input about what decisions result in what outcomes, and what the outcome “feels” like.
And if it comes time to change one or many of those decisions later on in this codebase, the person doing it gets a uniform codebase to work from! Unique abstractions and fixes in random places makes refactoring harder.
Or it's not an obsession.
It's caring.
Very few people can pull off a Steve Job level of nitpicking and actually finish a project.
I certainly couldn't, and that advice is for young me.