August 26, 2007
@ 07:18 PM

Inspired by this.

My Working Theory: Average Developer Ability to Perform Career Calculus = 1 / Volatility of Job.

This doesn't hold for "great developers" (ex.: Jim Little, Michael Nelson.) They learn because they enjoy it. They would be learning the same stuff if they were working as longshoremen.

I don't think it goes for developers in places where the management encourages growth either (like Solutions IQ), but I've never worked in a place like that, so I'm not sure if it's just the developers I've met from these places, they don't hire weenies, or it's really the environment.

For me, maybe my motivation is my "packed bag": I've never worked in one place a really long time, and I am usually in some phase of culture shock. I always kind of keep one bag packed in case I have a really bad day and need the relief of moving on.

The place I work now has extremely low volatility. You could easily start here as a developer and work until you retire. There are many incentives to stick around, and overall, it's a really great place to work. If they need you to retrain for something else, it's unlikely that you'd get forced out, and they would probably make sure you had access to whatever training you needed.

Unfortunately, this means that most developers don't get a lot of push to spend personal time and effort keeping their saws sharp when they've already got the job.

The thing I hear most often is that "there is more to life." True, but I don't think spending a small amount of personal time keeping your skills up to date is enough to impact a normal life. It's harder when you have a family, but not being able to spend, say, 5 hours a week sharpening sounds weak to me. If you can't even do that, you shouldn't be eating lunch.

I think this has been and continues to be one of the greatest problems in our industry today.


 
Thursday, August 30, 2007 9:06:37 AM (Pacific Standard Time, UTC-08:00)
>>It's harder when you have a family, but not being able to spend, say, 5 hours a week sharpening sounds weak to me.

This seems like a good candidate measuring stick to me. Are you into software development for the "the money", or do you actually enjoy your job? I want to work with people who enjoy their trade.
Tuesday, September 04, 2007 11:38:16 AM (Pacific Standard Time, UTC-08:00)
Remember what Frank Zarno used to talk about: Interviewing for your own job? I guess if you take that approach, you always have the reaper behind you somewhere, and that the impetus to keep your mad skillz sharp.

My biggest problem is sorting out 'what' to spent my 5 hours on. I know I have a limit to my free time, so I need to make it count. Usually, I refer back to those little irritating things that took way longer than I felt they should (i.e., looking up that regex expression for the um-teenth time, setting up a couple of macros in ultraedit, or learning about watir so I can scrape web pages.

As far as management encouraging growth, it depends on your definition of management. I have been lucky enough to work for developers who happen to be managers, or have responsibilities that closely resemble management (i.e., PJ, Josh.) These folks lead by example. "Hey I was playing with LINQ last night and..." That lights the fire under me to think, "Oh crap, I better start looking at that!" Its really about peer envrionment, IMHO.

We are going to start developer lunches (read "Code Brew"), where we join together, eat and discuss what folks have been working on in their spare time or at work. I think if your dev community is that interested in 'code play', then it almost feeds itself.
Jim Little
Tuesday, September 04, 2007 11:38:44 AM (Pacific Standard Time, UTC-08:00)
Remember what Frank Zarno used to talk about: Interviewing for your own job? I guess if you take that approach, you always have the reaper behind you somewhere, and that the impetus to keep your mad skillz sharp.

My biggest problem is sorting out 'what' to spent my 5 hours on. I know I have a limit to my free time, so I need to make it count. Usually, I refer back to those little irritating things that took way longer than I felt they should (i.e., looking up that regex expression for the um-teenth time, setting up a couple of macros in ultraedit, or learning about watir so I can scrape web pages.

As far as management encouraging growth, it depends on your definition of management. I have been lucky enough to work for developers who happen to be managers, or have responsibilities that closely resemble management (i.e., PJ, Josh.) These folks lead by example. "Hey I was playing with LINQ last night and..." That lights the fire under me to think, "Oh crap, I better start looking at that!" Its really about peer envrionment, IMHO.

We are going to start developer lunches (read "Code Brew"), where we join together, eat and discuss what folks have been working on in their spare time or at work. I think if your dev community is that interested in 'code play', then it almost feeds itself.
Jim Little
Tuesday, September 04, 2007 6:35:41 PM (Pacific Standard Time, UTC-08:00)
Cool! Code Brew! I love that name.

We have been trying to do a brown bag thing, but once again, it's all about participation. Like Sneal said, "people who enjoy there trade."

I will pitch Code Brew and see how it goes. There is a guy at work, Michael Nelson, who I used to pair with when we were in the same group. He would be up for it and we could spend more time doing cool stuff. If other people see us having fun, they might want to participate more.

Thanks for the idea!
Comments are closed.