Mankind was never meant to be perfect. A person is capable of developing bad habits with and without reason. Sometimes we are unaware of our bad habits and all we need is somebody to shed light on them. Like life, programming has no hard and fast rules; sometimes you wing it to win it.
However, at the end of the day, you have to differentiate between wrong and right. Breaking a bad habit can be extremely challenging, especially for developers. But the thing is, once they abandon these toxic practices, they themselves and the people around will become much more tolerable. Here are 7 awful habits that are cumulative of a larger number of traits found within programmers:
Procrastination germinates from laziness – momentary freedom is the objective. This usually happens when a programmer thinks that he/she has ample time until the deadline. They keep piling up tasks for the next day and that next day does not approach until it’s too late. They tend to forget that there’s a time and place for everything, and realization only occurs at the 11th hour.
Sometimes there are bugs that need to be fixed ASAP, but are dragged to the end of the project. Developers convince themselves that they are minor issues and forget about them soon after. Immediate attention is always an easier and efficient option. Later, it becomes harder to track the exact location of error; solving the problem then becomes a lingering headache.
Assuming Oneself as the Center of the Universe
These people are impossible to work with and are actually a curse for the team. Leader or not, they will act like the boss and expect everyone to follow in their footsteps. Developers retaining this habit like to write code in their own style without considering whether it’s compatible with what other team members are doing. They only visualize ‘I’ so they don’t care if ‘we’ can or cannot decipher their code.
Programmers suffering from superiority complex will always think that their approach to everything is optimal. They’ll enforce their tools and their ideas even if they are not the best ones in the room. They do not handle criticism well and will retaliate like you’ve wronged natural selection. All that this kind of people need is a whopping reality check.
Playing the Blame Game
Some programmers will never admit their mistakes at any stage of the project. If something goes wrong, they’ll blame another team member for messing up. If that’s not an option, they’ll blame the computer, their dog or maybe a supernatural force.
People with this habit will go as far as completely denying that they wrote the code, which was discovered to be faulty. Even when a problem is identified at an early stage, they will do anything to cover up their negligence. Accepting mistakes and learning from them is the right way to go. Taking responsibility for your actions and apologizing will not devalue your position.
As a programmer, you need to know how to write good and bad code. Sometimes optimizing every detail is not worth the time and effort that you put into it. Any improvements necessary can be made at the end; disturbing flow for the slightest gains is not a smart move.
Some clients will give you unrealistic deadlines, and that is when you’ll have to deliver rushed code that is enough to get the job done. The lack of quality is not your fault and you should comprehend that. Also avoid over-engineering tasks that can be solved through an easier method; seriously, you’re doing good to nobody.
Perfectionists cannot fight the urge to interfere when they see others making a mistake. They’ll use every opportunity to show the world that they know better and even engage in workplace politics to prove their point.
These developers are just selfish and stubborn. They will not make use of others’ knowledge and neither will they share their own experiences. Even when they’re stuck, they don’t consider looking up their problem on Google or referring to the several developer communities available online.
You might think that you’re one of a kind, but that’s highly illogical. Don’t hesitate to ask a question to the person sitting next to you and be grateful when someone is willing to lend you a helping hand. Somewhere someone encountered the same or similar issues that are giving you a hard time. Why not benefit from their know-how instead of tormenting your nerves? Also, if you come up with an awesome solution, let the world know. The give and take relationship is sadly underrated nowadays.
Knowing the tools you work with on a daily basis is fundamental to evolve into a brilliant programmer. You should know how to solve problems instead of giving up when you’ve reached the brink. It is a common practice to copy-paste code that is easily accessible through open sources on the internet.
Using someone else’s code is not a crime; it’s available to the public for a reason. Nonetheless, blindly practicing this technique is the real concern. When employing another developer’s code, you must first read it from the beginning to end. Only go ahead once you’ve fully interpreted all its elements.
Ignorance is bliss, yet not when you’re programming. Do not overlook errors in your code if it’s still working, because it is going to haunt you later. If someone tells you that what you’re doing is wrong, listen to them instead of telling them off.