Aim Higher!

Posted by Stuart Herbert on July 26th, 2012 in Opinion, PHP In Business.

At the start of the month, I was on a panel at Unified Diff (which, if you’re in the South Wales area, is well worth your time going to every month), and the last question we had is well worth expanding into a blog post. We were asked what each of us would do with a failing developer, and everyone was taken aback by my unequivocal answer: I’d fire them. After some back and forth between us (which carried on over a pint afterwards), my fellow panelists concluded that I seemed to be able to afford higher standards than they could in their organisations.

And that comment really struck a chord with me.

Fire Failing Developers

So why would I fire the failing developer? By keeping that person on you’re damaging the morale of the rest of the team, and you could end up losing good people and being stuck with the one you should have fired in the first place. (Guess who learned this one the hard way!) You’re also wasting your firm’s money on the person, you’re probably damaging your product, and if the person has any direct contact with your customers, you’re probably damaging your firm’s reputation there too.

Can you turn a failing developer into a star developer? Perhaps, and you should definitely try to do so. In fact, that’s part of your job – to spend every single day trying to turn every developer you manage into a star in their own right. Never wait for someone to start to fail. If you’re doing your job right, then when someone reaches the point where they’ve become a failing developer, you’ve already done all you can about it.

I’ve had to do it a few times over the years, and it feels bloody horrible every time. It’s not a nice thing to have to do, whether it’s an employee or a supplier. I always want to see the best in someone, and I always want them to have the success they deserve. But it’s part of the job, and you do no-one any favours by not facing up to it if it has to be done.

Why Do You Aim So Low?

What about higher standards? How come I seem to be able to afford them when others feel they cannot?

When I was a kid, I sat a lot of exams throughout my school years, but I was never remotely interested in how well I’d done versus everyone else. What I cared about was measuring myself against what was possible. How high could I consistently score? What was the next level up of test that I could sit? What could I learn from other sources? How could I apply it, play with it, really get inside it to start to actually understand it a bit? Where did the hard work need to be put it to take it further still? How could I have fun with it?

I’ve applied this approach to everything I do, whether it’s software engineering, writing, speaking, music, photography, or my martial arts. And I have found it to be liberating. My constraints are my slow-witted mind, my somewhat broken body, and the march of time … and I am in competition not with you, and not with failure, but only myself.

In a world of frankly very low standards, if all you do is measure yourself against the people around you, then it really doesn’t take much to seem like you’re doing pretty well. There are a lot of advantages to being ahead, it’s true, and evolution does favour the lazy … but you’ll never amount to anything much, and you’ll never achieve anything worth a damn if you don’t lift your gaze, look out to the stars, and see what can really be done.

This world is full of people with amazing potential, who never realise that potential. They’re just a waste of space. You can be better tomorrow than you are today. Aim high. You can do it. Everyone can do it. You just have to choose.

We don’t have a lot of time to achieve things in life, and as you get older, you become more and more aware of just how quickly the days are passing. Every day you spend just trying to get through the day … you can’t get that day back. It’s gone forever. And you never know when fate is going to cut your days suddenly short. Make the most of them. Achieve something worth while, and aim high when you do.

7 Comments

  1. phpcodemonkey says:
    July 26th, 2012 at 7:45 am

    Love how your thinking in this post is exactly aligned with how I operate. I’ve had to let a developer go already this year, we still have a vacancy because of that move some three months later. However I’d rather have that than the wrong person in the team! My role as the manager in our agency is to raise the bar on everyone around me, ‘how can we do that better/more quickly/more efficiently?’ so that we continue to grow our reputation for the right things. There is always a danger that one person can destroy that, so if staff aren’t aligned to the goal of bettering themselves, as you say Aiming Higher, then they may be pulling your company, either by lack of or deliberate action, in the other direction which will certainly not enhance the right kind of reputation.

  2. Stephen S. Musoke says:
    July 26th, 2012 at 10:41 am

    Yes, you need to fire them as soon as you can, otherwise they will drag you down and you still need to fire them later.

    The question is how do you determine that the developer is failing and not the surrounding processes, managers, leadership, clients, technology, tools?

  3. Zilvinas says:
    July 27th, 2012 at 11:27 am

    I liked your post especially measuring against yourself part. However saying “They’re just a waste of space” is not cool to say especially since there’s no definition of life’s purpose but the one you’ve made-up yourself ;)

  4. Andreas says:
    July 27th, 2012 at 2:34 pm

    I’m curious. Wouldn’t the first issue be to define a failing developer as to what is a failing employee?
    From reading this I have no clue what a failing developer is other than someone that is a virus contaminating “everything” and “destroying” businesses. Like you wrote “probably damaging your product, and if the person has any direct contact with your customers, you’re probably damaging your firm’s reputation there too.” But can’t see that as anything developer specific.

    From what I can tell a failing developer is someone that does not live up to your expectations, but this is odd given how you in the last half of the article go on about how you should only compare to yourself.
    Also saying that someone aims low because they don’t aim to where you do is quite condescending. They could just be happy where they are and there is nothing wrong with that. Its like the story of the businessman and the fisherman. http://www.ijourney.org/?tid=70

    So would be good if you could define a failing developer as say a regular employee? What is a failing developer?

  5. Phillip says:
    August 5th, 2012 at 3:18 pm

    I do not know the exact definition of a failing employee or failing developer but I can tell you this boldly that not all people in many organizations have high aims. Half of a team even in big corporations today are made of “free riders” who hardly contribute anything to the team, leave alone aiming high. The interesting fact that I have noticed about these free riders is that though they may not be good developers but they are good bullies and they cannot be fired because they know how to manipulate an organization/management.

  6. Shiv Modi says:
    August 7th, 2012 at 6:29 am

    Really like the post, specially the last paragraph and the line “..and I am in competition not with you, and not with failure, but only myself.”

    Well Said!!!!!

  7. Apps Promotion says:
    August 8th, 2012 at 11:24 am

    The paragraph you add “However I’d rather have that than the wrong person in the team! ” is totally right because most of the time it happen in the team work and your firm is got effected.

    Thanks for sharing your knowledge through these words