There are two sets of skills that a good software developer needs to cultivate: technical skills, and non technical skills. Unfortunately some developers focus only on the technical part. When this happens they will develop some bad habits from which the following are the 5 top non-technical mistakes:
1.- Lack of discipline.
“Discipline is the bridge between goals and accomplishment.” Jim Rohn.
I’ve always thought that discipline is one of the most valuable skills, not only for being a software developer, but to be successful at any other area in life It is also true that usually it is very hard to find people who are both brilliant and disciplined.
Steve Pavlina highlight the 5 pillars of self discipline… “[...]Acceptance, Willpower, Hard Work, Industry, and Persistence. If you take the first letter of each word, you get the acronym “A WHIP” — a convenient way to remember them, since many people associate self-discipline with whipping themselves into shape.[...]” I highly recommend to read his series of articles in self discipline.
My personal approach is to follow these steps every day.
- Have your own to do list for the day
- Do one thing at a time
- Do it right
- Don’t finish something until it’s completely done
- Better late than sorry BUT better sorry than never.
2.- Big egos
My experience says that big egos and programmers go hand by hand, the main problem of having a big ego is that it actually prevents you from realizing that you have a big ego, a few indicators that may help you to know if your ego is way too big are:
- You consider yourself the best programmer.
- You block conversations.
- You ask for code reviews not to get criticism but to show how good your code is.
3.- Being a bad communicator.
“If I am to speak ten minutes, I need a week for preparation; if fifteen minutes, three days; if half an hour, two days; if an hour, I am ready now“. Woodrow Wilson
As human beings communication is our main activity. Being a good communicator is hard but essential in our profession, we are continuously exchanging opinions about designs, code, having peer reviews, writing documentation, trying to convince someone else that our design is better, writing code…
Good communicators are those people that when they are explaining something, their explanation is:
Focus. They just talk about what is need to be understand.
Clear. Easy to understand.
Concise. Nothing to be added, nothing to be taken.
For being a better communicator, I have two advices:
If you think you are not a good communicator, prepare what you are going to say until is focus, clear and concise.
If engaged in a conversation, first listen, then think and then talk.
4.- Forgetting about the customer.
“If we don’t take care of the customer… somebody else will.”
You are there just for one reason- your customer. It’s easy sometimes to forget this point. I have been in teams where focus was on technologies and platforms rather than in having a happy customer. We would expend months creating a framework that didn’t deliver any value to the customer, and by the time we were about to start using it, we would discover that it won’t fit our user needs.
5.- Not prioritizing the work properly.
Developers who are always gold plating, researching new and more interesting technologies, over engineering solutions or just doing whatever they find more cool are impediments to the project, I’m not saying that is not normal to engage into lateral activities from time to time, we all need distractions, but if you find yourself usually in the previous situations you may reconsider the way you prioritize your work.