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.

This is how you Code Like A Boss 😎.

--

--

--

🚀 Helping aspiring developers land their first job and move up fast. ⏱ 15+ years industry experience. 👉 Visit bossprogrammer.com.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Build tools you can trust, not just use

Install Theme in Drupal 9

3 Perspectives I Uncovered From The Pragmatic Programmer

Building a bot on Slack

Wrangling cloud costs

Authorization with Casbin in Apache APISIX

How do malloc & free work in C

Web Application in 10 minutes with Streamlit

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Boss Programmer

Boss Programmer

🚀 Helping aspiring developers land their first job and move up fast. ⏱ 15+ years industry experience. 👉 Visit bossprogrammer.com.

More from Medium

Top 10 git commands for developers

Essential Technical Aspects

Why you no?! — Iterative Refactoring