Why Did You Become A Software Developer?
As it is still a relatively young profession, it's interesting to see why people became software developers. It can be a fantastic question to ask at an interview, as an honest answer gives you real insight into how passionate someone really is about developing software, or at least can help guage potential. A lot of the time people are simply in it for the money. Other times I find that people have fallen into the industry - they had a different idea of what their degree would lead to, and ended up somewhere completely different. Although this happens, it's not necessarily a bad thing.
I'd like to see why readers decided to become a software developer. After voting, please leave comments to give us some more insight. Perhaps, more importantly, how can we encourage new graduates to join the software industry


Comments
James Sugrue replied on Tue, 2010/05/04 - 1:10am
While money definitely had a bearing in my final decision, I think I was always destined towards the software development industry. When I was younger I messed around with BASIC a little, and even though the games I created were simple (and just copied out of some BASIC book), I was amazed by the potential. I did have ideas of becoming a game developer, but I never got around to that. Now, I can't see myself doing anything else apart from writing or designing software.
James
Ivo Limmen replied on Tue, 2010/05/04 - 1:19am
Zqudlyba Navis replied on Tue, 2010/05/04 - 1:49am
Because I'm looking for intellectual stimulation and being able to build something concrete with my bare hands...something tangeable. I want to be able to come home some days and say "I built something fun and useful today".
I had a stint as a project manager for 13 months and I didn't find it intellectually stimulating, so I went back to coding. As a project manager, at the end of each day, I couldn't say to myself "what useful stuff did I do today", because most of the time I was in useless meetings, phone calls, interviews, presentations, pushing paper (ms word) or creating power bloody point slides. All those project management stuff are actually administrative secretarial duties that could easily be done by not so bright high school drop outs.
Here's a useless business analyst at Initech from the movie Office Space. It reminds me of a useless Pointy Haired Project Manager
http://www.youtube.com/watch?v=Ti53kjHsAas
"I deal with the god damn customers so the engineers don't have to. I have people skills; I am good at dealing with people! Can't you understand that? What the hell is wrong with you people?"
Bogdan Marian replied on Tue, 2010/05/04 - 2:29am
Gabor Farkas replied on Tue, 2010/05/04 - 3:06am
Radek Jun replied on Tue, 2010/05/04 - 3:26am
Fabrizio Giudici replied on Tue, 2010/05/04 - 3:34am
Endre Varga replied on Tue, 2010/05/04 - 3:57am
I started programming with a 286 in QuickBasic. I learned the language from the help files :)
At the end of High School I wanted to be an economist (!), but changed my mind after seeing what technical universities offer, and finally applied for CompSci. It was a good decision ;)
Endre Varga replied on Tue, 2010/05/04 - 4:17am
Also it would be interesting to see, how our primary language choices evolved over time.
For me, it is: QuickBasic -> Pascal -> Delphi (ObjectPascal) -> C -> C++ -> Java -> Scala
James Sugrue replied on Tue, 2010/05/04 - 4:19am
in response to:
Endre Varga
Good idea
Mine would be Basic -> Pascal -> Java -> C/C++ -> Java
Chris Treber replied on Tue, 2010/05/04 - 5:55am
I made my long term hobby my profession (started out with 6202 kit, TI-58, TI-59, Commdore PET, C-64, Atari ST)! My chain of languages: Commodore Basic, 6502 Assembler, Atari Basic, Visual Basic (this is an embarassing amount of Basic!), C++ (3 years), Java (12 years).
Chris
Wujek Srujek replied on Tue, 2010/05/04 - 5:47am
I started on the 3rd year at uni (5 years in total), last year I worked for a company.
asm -> pascal -> (proper larning) java / bash :D -> freedom (I learn what I want and when I want: python, scala, ....)
Now I have been doing this for almost 3 yrs profesionally (which makes my overall programmer career 5 yrs long). I feel like a newbie :D
Piero Sartini replied on Tue, 2010/05/04 - 5:49am
I got my first IBM PC with 7 years.. it was a huge device. But since then I was interested in how computers work and what I can do with them.
Languages: BASICA -> QBASIC -> PowerBasic -> TurboPascal -> C -> PHP, JavaScript -> JAVA .. and now some JVM languages like JavaFX, Groovy and Scala. Learning never ends.
Fred Gracely replied on Tue, 2010/05/04 - 7:20am
John Conner replied on Tue, 2010/05/04 - 7:40am
Guillem Plasencia replied on Tue, 2010/05/04 - 8:17am
Tim Berglund replied on Tue, 2010/05/04 - 9:02am
Gregor Kovač replied on Tue, 2010/05/04 - 9:04am
Jose Luis Monte... replied on Tue, 2010/05/04 - 9:20am
Dale Wyttenbach replied on Tue, 2010/05/04 - 9:23am
Michele Mauro replied on Tue, 2010/05/04 - 9:33am
Antonio Antonelli replied on Tue, 2010/05/04 - 9:39am
The Rpk67u replied on Tue, 2010/05/04 - 9:50am
Peter Veentjer replied on Tue, 2010/05/04 - 9:53am
For me the most important aspect of creating software, is the technical challenge and visualising how something should/could look. Structuring chaos..
Peter Veentjer
Multiverse: Software Transactional Memory for Java
http://multiverse.codehaus.org
Marco Rietveld replied on Tue, 2010/05/04 - 10:11am
Once upon a time, I was premed student, but organic chem was too hard -- and comp. sci was cool.
Then I was a comp. sci student, but it was too abstract -- so I got a job as a sysadmin (and kept studying).
Then I was a systems administrator (sysadmin) -- but people only spoke to me when they were problems and my colleagues were weird. So I got a job as an (information) analyst.
Then I was an (information) analyst -- but I never got to really make anything. I was just analyzing.. and I missed the code and started reading books about code. My housemate saw that one day and said "Why aren't you a developer?"
And now I'm a developer! People ask me to make things, and I get to make them! And when I need to, I end up playing "information analyst" or "sysadmin". :)
(Ironically, when I graduated from university, the last thing I wanted to be was a developer: I figured I'd end up working on a small part of the system, never get to see the whole thing and sit in a corner all day in front of a computer. None of those ended up being true.. )
Clure Rogre replied on Tue, 2010/05/04 - 10:16am
Javier Fernández replied on Tue, 2010/05/04 - 10:28am
Sean Patterson replied on Tue, 2010/05/04 - 10:30am
Mean Variance replied on Tue, 2010/05/04 - 10:36am
I sort of stumbled into software development. I was doing tech support for enterprise software (Essbase) in the mid 90's. No one was taking ownership of supporting the Visual Basic APIs that customers used, so I took the time to learn. As I started to transition my way to the QA group, the development group offered to interview me and take the chance of brining a junior developer in. I jumped at the chance.
I learned C from the pros in the development group and was off running. Later another company took a chance at hiring me as a Java programmer, again not knowing the language. Now, I've been programming Java for 11 years. Right now I'm trying to learn Objective C (and it hurts!).
Dave Leblanc replied on Tue, 2010/05/04 - 11:01am