Here’s a good advice for playing Chess:
"Don’t move until you see it"
There’s one best move to make and it’s your job to find it. It’s much easier to take the first move that seems good enough. It’s much harder to think each move through and follow the consequences. The ones who have the patience and stubbornness to do so - win.
I’m not a Chess player, I barely know the rules of the game.Software Development
I’m a developer and I’d like to offer a different advice:
"Move until you see it"
The development process is also full of small moves.
- How should I name this method so my teammates understand it?
- Is it okay to use a global variable for this bug-fix?
- Should I encapsulate this in a new object?
- What framework should I use to solve this task?
Each task can be solved with many different moves. Some are very poor choices, others might be okay and some are pure genius. Yes, even in programming, some “moves” are better than others.
One of them is the best. It’s your job to find it.
In Chess, you only get one opportunity to take the correct move, but programming allows you to play around and find it.
So move a lot and start seeing it. It happens that the simpler moves to spot are the poor choices.
Yes, it’s easier to add a global variable to solve a bug, but what goes around comes around and that small hack will hunt you in the future. And yes, it’s easier to copy-paste code instead of making things DRY, but then each change multiplies work.
So go play and find the right move. And keep moving until you see it.
Let’s talk about this on Twitter, I’m @ketacode.