Why why why why why are you a developer?
July 6, 2011 § 14 Comments
Recently, I’ve been thinking about slowing down and doing what my brain is trying hard not to do, THINK about WHY I’m doing this. The real question I need to answer is… WHY am I developer?
The 5 whats?
The 5 whys is a technique used by Toyota to get to the core cause of a problem. It’s part of their legendary lean methodology and in recent years it’s been used as part of Eric Ries’ Lean Startup movement.
5.times { ask "_why" }
You take your problem and through the application of the 5 whys you can establish its root causes. While being a software developer isn’t exactly a problem, I think that the technique can help reiterate the root cause for our decision to become developers. So, let’s give it a go:
WHY am I a developer?
- To write beautiful Ruby code. But why?
- To create a product that people love, with a language I love using. But why?
- Create a solution to a real problem that people have, and for me to love doing what I do. But why?
- Being creative and to be part of something that makes people’s lives a little easier. But why?
- To make a positive impact with what I create, both to others and myself. But why?
- Happiness. My own and those who have direct or indirect contact with me and my craft.
Wait…in 5 lines have I gone from a code monkey to a hippy? No, I just now know WHY I’m doing this. It turns out that despite the fact I spend most of my day in code that’s NOT the real reason I’m a developer, in fact I haven’t really mentioned code since the first why! I’m here to build something and it’s not about the code, the syntax or test coverage, no matter how useful these are.
So what can all this tell us?
By understanding the core reason for you being a software developer you can cut the crap. Is moaning about other people’s products your number 4 or 5? No? Then stop wasting your time doing it. Remembering why you love building awesome systems, that make people’s lives easier, will make you happier and more productive.
Personally, I’ve learnt that I’m a developer to build products that make me and others smile. Right now that’s through coding with a language I have a serious man crush on (Ruby), with a team of awesome people (Mint).
Personally, I’ve learnt that I’m a developer to build products that make me and others smile. Right now that’s through coding with a language I have a serious man crush on (Ruby), with a team of awesome people (Mint).
Making a career path out of a maze.
I think your core reasons can also be beneficial when looking at your career path. If money is amongst your core reasons then think about joining a bank (and silo your knowledge), if it’s about product try a startup (and diversify your skills). I’ve found it all too easy just to go with the flow and stick my head in the sand with the hope that my career will just pan out. It might do, but probably not the way I’d hoped, unless I keep to my core values. I’ll carry on coding and creating; I just hope to do so consciously.
Why are you a developer? I’m intrigued as to whether there are a variety of answers or if it all comes back to the same reason. Feel free to use the ‘five whys’ and post your results below.
My reason pretty much stops at #3 on your list, where I just enjoy solving problems and the sense of satisfaction it gives me. For me, #4 and #5 in your list are just good side-effects of that, but not my true aim.
hi Paul,
Those answers are just my own rather than me saying all developers will have the same. I think if you keep burrowing down you’ll answers after your second why.
I think the real benefits come from not just the answer to the 5th question but also looking back over all your answers and just stopping to ask yourself the hard questions.
I see where you’re coming from, Paul. I remember writing that sort of thing down on my application to university. Problem solving does have a sense of satisfaction, but each problem is just part of the journey to somewhere and I think that’s what Simon is getting at.
I’m not sure what my answers to the 4th or 5th why are, but I guess this post has certainly made me start to properly ask myself.
Simon, did you find the answers came easily, or did you have to think/discover them over a longer period of time?
hey Phil, I definitely found the later whys hard and even went back up the why stack once or twice. I think the fact that it’s a challenge indicated to me that this was beneficial, it might seem hard or even a pain in the ass but it’s a lot less painful than going down a path that will make you unhappy.
Good luck with your whys!
Very interesting post, thanks…
BTW, congrats on getting engaged! Was that decision the result of a 5 why’s process?
I think I’ll start applying this technique to more aspects of my life. I think past the 3rd why you start to become truthful with yourself. Really interesting post, thanks!
To be brutally honest, I am a developer because it is one of the few desk jobs that an inarticulate verbally-challenged, slightly disabled person can make over $40K a year.
Best answer I’ve heard!
Is’t that the way ?
[…] 本文是从 Whywhywhywhywhy are you a developer? 这篇文章翻译而来。 […]
[…] 导读：本文是从《 Why why why why why are you a developer? 》这篇文章翻译而来。译文来自外刊IT评论《为什么你要做一名程序员？》。 […]
[…] historically used to diagnose mechanical problems in their cars, and I recently read about it on Simon Reed’s blog about his choice of […]
[…] 原文：Simon Reed 译文：外刊IT评论 […]
[…] 原文https://logicalfriday.com/2011/07/06/why-why-why-why-why-are-you-a-developer/ […]