Skip to main content

Don't promote your developers

Yes you read correctly. Don’t promote your developers. They deserve to stay where they are.

Having worked for a number of companies who believe the only way to show their appreciation for hard working developers is to give them more responsibility, I am a firm believer in doing the exact opposite. Companies move successful developers into other areas of their business, often into people management, and take away what makes the developer good at their job, or at the very least dilute their skills by asking them to focus on people rather than code. But there’s a reason your developer is good at what they do. Most developers are not ‘people people’, they are software people and for very good reasons.

If the software development team is writing the core product or system the business is using day-to-day, moving those developers away from developing will have a significant impact on productivity and quality. Even promoting a developer to an architect, for the purposes of paying them more, is often wrong. Software architects are not the same as building architects, they still need to code and code regularly. Obviously there are exceptions to the rule and a developer may want to make a career change. If they want to move to something very different, let them. If they want more responsibility, make it over the design and or make them the team or project technical lead, but make sure someone else does the people management of the team.

Perhaps some companies feel the need to justify the pay rise on offer, giving the developer more diverse responsibilities in order to do so, but why would you move someone from a job they excel at into a job they’ll struggle with just to pay them more money? Tech firms need to understand that their software developers are at least as important as their people managers, if not more so, and recognise the importance of technical excellence. The solution as a business owner is to keep talking to your developers, make sure they’re doing what is best for them, and your business, and regularly increase their pay in line with everyone else in the company. A good developer is a valuable asset, so reward them by letting them shine in their role. Listen to what they have to say and let them manage code, not people.

Ideas: Paul Grenyer
Words: Lauren Gwynn

Comments

  1. Yes, you’re absolutely right! I spent several years as a developer – I always knew that I’d be best employed as a developer, and not in people management.

    Have you read “The Rosie Project” by Graeme Simsion. This book should be on the reading list for all us IT people!

    ReplyDelete

Post a Comment

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv

Bloodstock 2009

This year was one of the best Bloodstock s ever, which surprised me as the line up didn't look too strong. I haven't come away with a list of bands I want to buy all the albums of, but I did enjoy a lot of the performances. Insomnium[6] sound a lot like Swallow the Sun and Paradise Lost. They put on a very good show. I find a lot of old thrash bands quite boring, but Sodom[5] were quite good. They could have done with a second guitarist and the bass broke in the first song and it seemed to take ages to get it fixed. Saxon[8] gave us some some classic traditional heavy metal. Solid, as expected. The best bit was, following the guitarist standing on a monitor, Biff Bifford ripped off the sign saying "DO NOT STAND" and showed it to the audience. Once their sound was sorted, Arch Enemy[10] stole the show. They turned out not only to be the best band of the day, but of the festival, but then that's what you'd expect from Arch Enemy. Carcass[4] were very disappoin

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th