Programming == Thinking
For the past 15+ years I’ve seen programmers make the same mistake.
They type first, and think later.
This is probably a by-product of the shift from Waterfall to Agile – or maybe just laziness, but it’s going from one extreme to another.
Do you know the mantra of carpenters? Measure twice, cut once.
There’s much for programmers to learn from this.
If you type first and think later, you’ll end up re-writing your code, and probably not just once. You’ll cost yourself or your company time and money.
So before you put those fingers to the keyboard and satisfy that itch to start typing, you need to consider:
- Functionality
- Usability
- Reliability
- Performance
- Supportability
This doesn’t need to be a long, drawn out process, but time does need to be given. If you don’t, you’ll end up in cycle of hacks and re-writes.
So the next time you code, remember to think first and type later.
