Why Developers Get Fired: Page 2


You Can't Detect What You Can't See: Illuminating the Entire Kill Chain

On-Demand Webinar

Posted September 20, 2009

Eric Spiegel

Eric Spiegel

(Page 2 of 2)

A second reason developers are shown the door is that they aren’t communicating the great results of their work. If you think cranking out tons of code from the safe confines of your cubicle will ensure your job security, think again. You have to promote your work.

Yes, I mean brag.

You cannot always rely on your manager to communicate your successes with others on your team and in management. Take management out of the equation and start a peer award process where the team members vote on “coder of the month” award.

Provide some goofy trophy and post the winner (and what they did) on the company wiki or via email distribution list.

You can also subtly mention what it is you’re working on with others in management or end users. If you are doing good work, then you’ll receive kudos when the software is implemented.

And if the implementation is not a success? This is tricky because you don’t want to play the blame game in public.

One suggestion is to talk openly about things that can be done differently next time and how you are eager to work with the team to correct the problems. However, if failures keep happening then follow the actions from my first reason above.

Finally, a third reason. This is the one that drives managers crazy. It’s the case of unfulfilled potential.

The developer who has all the talent in the world, but lacks either motivation or drive to perform up to expectations. As a manager, I expect to be able to motivate team members with money, career advancement, cool projects or even intangibles such as increased work schedule flexibility.

But sometimes, the rewards just don’t motivate.

The result is a developer who isn’t accountable. They consistently are late to work and meetings. They don’t adhere to standards. They’re simply complacent.

Sometimes really smart developers can get away with this for a period of time. They can write code in a fraction of the time it takes others. Yet the manager allows for the same time an average developer would take to complete the same code.

The problem is when the developer gets too lazy or too cocky and starts pushing their deliverables to the last minute, causing delays. Or they just aren’t around when other developers need to talk to them. Eventually the ax will come down on them as well – the manager must look out for what is best for the team and long term success of the organization.

You can be sure that there are plenty of other reasons developers get fired. So take off the ear buds, close down your 20 Skype threads and take some time each day to think about what you can do to prevent this from happening to you.

Otherwise, don’t feign surprise when you also hear the words “You’re fired!”

ALSO SEE: Are These Developer and IT Salary Figures Accurate?

AND: Finding The Coding Zone: Your Perfect Trifecta?

Eric Spiegel is CEO and co-founder of XTS, which provides software for planning, managing and auditing Citrix and other virtualization platforms.

Page 2 of 2

Previous Page
1 2

Tags: management, developers, developer salary, programmer salary

0 Comments (click to add your comment)
Comment and Contribute


(Maximum characters: 1200). You have characters left.



IT Management Daily
Don't miss an article. Subscribe to our newsletter below.

By submitting your information, you agree that datamation.com may send you Datamation offers via email, phone and text message, as well as email offers about other products and services that Datamation believes may be of interest to you. Datamation will process your information in accordance with the Quinstreet Privacy Policy.