Common Perils that Persist for Programmers
Earlier this week, we investigated some of the pitfalls programmers can face when it comes to productivity. Now we round out the discussion and tie up loose ends in the perils of programming productivity pitfalls. Click here if you missed the first discussion, and click here if you missed the second discussion.
Pitfall #11: Poor Documentation
Ever finish troubleshooting an error after countless hours only to have it pop up again later down the road and realize you have no idea how to fix it now? Well, that can be avoided if you keep detailed documentation that is readily available. Even if you don’t have the error again, chances are you are going to save someone else hours of frustration when they have a similar issue.
Pitfall #12: Overdocumentation
You won’t find many who will admit that their slavish devotion to documentation has actually hurt their production, but the truth is that it can. By repetitively recording the same information and relentlessly detailing every step, you are keeping yourself and the project from advancing. The best solution is to use your technological prowess to your advantage. Avoid retyping when copy-and-paste can do the trick, and keep an eye on word counts when setting a limit for explaining certain aspects of a project.
Pitfall #13: Nonprogrammer Managers
Managers with no background in programming can be a project's nightmare. They can lack understanding of coding concepts and be unable to make educated decisions. The best approach is to have patience and to make sure the lines of communication are open. Help nonprogrammer managers learn the inner workings with a tactful approach that is nurturing without being condescending. This will allow them a better perspective on and appreciation for the work being done on the project. And remember, they are managers not because they are experts but because they are great at getting their experts to create value.
Pitfall #14: Programming Managers
Managers with programming experience can feel that their way of doing things may be superior, even if their methods were abandoned long after they made the transition into management. They can also be micromanagers and become overly obsessed with the little details rather than the overall scope of the project. Patience is the key to keeping productivity on the upswing. Lifehacker suggests you be proactive in communication and do your job well enough that programming managers aren’t in the habit of trying to go back and iron out small details.
Pitfall #15: Brogrammers
"Brogrammers" are the epitome of frat house culture and value youth over experience. Hypercompetitive can be one way to describe these developers, as a mature, well-rounded approach to work life evades them. So, what is the solution to an office overrun by bros? Highlight great ideas and let jokes or bad ideas go unacknowledged. Also, make sure management establishes guidelines, and aggressively work to ensure that those who step outside the guidelines for appropraite office behavior are properly reprimanded.
Do any of these pitfalls apply to your company? Do you have solutions to these pitfalls? Did we miss any pitfalls? Tell us in the Comments.
