4 Moments When Playing Dumb as a Developer Makes You Smarter

Keep these things in Mind

Photo by Marco Lastella on Unsplash

Every developer want to write code smartly.

Nobody like to play dumb.

However, there are times when it is better to play dumb than to play smart. If being a bit dumb helps us write code quickly and make it more robust. What’s the problem with playing dumb with some of our habits?

Here I have mentioned four of those times when we should play dumb instead of smart.

1. Trying to think of good names

While writing code, a programmer spends most of his time thinking of good names.

We keep thinking and thinking.

Names come up in our minds and we keep discarding bad names in our minds.

There is a way to find a name very fast.

These are the steps

1. Have a clear purpose for why you are creating a particular name.
2. Once you know the answer to why question. Just write a name, whatever comes to mind. It doesn’t matter if it’s bad.
3. Again come up with one more bad name. This is the second bad name from your point of view.
4. Now, once again, you have to think…