I focused on one at at time, making steady
This week I've been deep in an epic coding session, worthy of the rousing soundtrack you get in Hollywood hacker movies. It's fun. And something interesting: In working on this application (doesn't matter what it is), I was stuck on an important subsystem. It had to do with how my application integrates with a complex vendor API - but again, that detail doesn't matter. What matters is that, when I started, I could see four possible ways to implement it. And it wasn't clear which was best. So I invested a good chunk of time spec'ing them all out. Reasoning how each would fit in the app's architecture... And after, I still couldn't tell if ANY of them would work. Or all of them. Or only one. (Which one)? As you get better at coding, you encounter dilemmas like this less often. Like a master chess player, you get better at "pattern matching" increasingly complex coding situations, and able to reckon which choice has the best chance of work