Grant Killian's Blog

No, this has nothing to do with beer -- but maybe it should?

.Net Breeds Workaholics?

Dang! I know I prefer posting code, but I feel moved to make this one less technical entry. I just finished giving a class on XML and ADO.Net and jumped online to check email before heading home. I responded to a few messages (some technical, some not) and -- this is the interesting part -- every person I responded to wrote me back immediately. I, in turn, responded to them and around-and-around-we-go. It's almost 9 PM here on the East Coast. These same people, including bloggers like Darrel and Mark, are online early in the mornings too. What is happening? Do all the people I work with, including myself, have a case of workaholism?

I know the programming subculture thrives on an almost frantic work ethic, but when is it too much? Besides class tonight and Weds, I'm giving a BizTalk and .Net talk tomorrow with a colleague. This is an unusually busy week for me, but it's not uncommon for me to work into the wee hours of the morning. Apparently, working beyond the 9-5 schedule is a standard in the software business. Does your employer even know or appreciate it? What about your family?

Speaking of family . . . I'll wrap this up and go home to dinner . . .

Published Sep 08 2003, 05:59 PM by grant.killian

Comments

Jason K said:

Maybe not working into the wee hours for my employer, but the driving desire to find my own little niche in the world does keep me awake late many nights. I think there's a principle that many people don't even that could be called something like "employer training". If you work overtime all the time, it's expected--if you don't, you appear unmotivated even. If you DON'T work overtime all the time, however, then the times you do are appreciated and praise is heaped on you by your employer ;) I'm almost emberassed to say it, but it works well for me. I got the idea from a Dilbert cartoon where Dilbert is calling his boss at 3 AM "Hi this is Dilbert it's 3 AM, I'm in my underwear and I'm thinking about you... ooops I mean..." Not quite to that extent obviously but you get the point!

# September 8, 2003 2:26 PM

Darrell said:

I also think it is important to set proper expectations with your employer. Start off a new job working 50-60 hours a week, and that will become "the norm." So for the past month at my new job I've been working no more than 45 hours per week (a very small amount in a consulting firm where people usually average 50-60). But then again, I think I get more done while I am there, since I am able to think straight! Or think in sets, since I am buried in a SQL Server data warehouse project right now... :)

# September 8, 2003 4:24 PM

Chris H said:

I'd have to say that most of the good programmers I know treat programming more like a hobby they get paid for than as work. Therefore most don't mind "talking shop" after hours. We're also natural problem solvers. So, like you, when someone asks a technical question, we're usually compelled to find the answer right then. Even when common sense overrides our natural tendencies, we usually don't stop thinking about the problem. Not completely anyway.

Personally, I don't find consistent overtime to be a good idea. If there's a need beacuse of a deadline then absolutely it's a must. but to work an extra 2 hours a day simply to be there seems a bit foolish. Especially if your project is on schedule and underbudget. Now I don't include in that any time spent working on your own things or studying/research. Those are things we must do off the clock simply to stay current with the industry. However still goes towards time spent doing work related things.

However if one day you walk in the door and your kid says to your wife "Mommy, who's that?" Maybe it's time to reevaluate our personal schedules. ;)

# September 9, 2003 5:42 AM

Grant said:

Good points -- there's certainly a balance to be found. Putting extra effort in seems to be part of the job description!

# September 9, 2003 5:56 AM

Dave Burke said:

I agree with everyone here, particularly Chris H who says most programmers view their "work" as a hobby for which they get paid. As for working overtime, I'm a telecommuter (for over 3 years now) and I try (try) to do non-employer stuff at night. That helps keep things balanced for me.

# September 9, 2003 4:18 PM