in reply to Interview Counterattack: "Show me a project-plan"

Uh .. I don't necessarily agree with the whole "Everything's got to be in MS Project" concept. As long as management and developers are talking and there's agreement that things are moving in the right direction and targets are being met, things are fine.

Yeah .. that may end the interview on a bit of a downer. If you've been on the operations side of software support, you know that unexpected things happen and overtime is required. It's probably better to ask an open question like "How do you deal with overtime?" or "How busy are you right now?" than it is to ask a closed question such as the one you suggest.

Overtime gets compensated -- my deal at $work[-2] was that I got double time off for a support call, so that a one hour call gave me two hours off, and if the call interrupted my sleep, I would just sleep in, have breakfast and get to work whenever I got to work; my employer was fine with that. If you're talking about development overtime, then I expect that, after the rush, the company would tell the developers to take a few days or a week off and go home and sleep.

But these days I can't believe that managers think they're going to get 50% more quality code done by getting their developers to work 50% longer hours. I think research has shown that after eight hours developers start to make mistakes, then have to spend time to fix those mistakes -- so you're not really any further ahead, and you may even be further behind if some of those mistakes were bad design decisions.

I started keeping a log book a few years back -- it was something my colleague Mike Stok did, and it's fantastic. Now when someone asks me something, I flip back in the book and read out the command I typed. That's way better than "Oh, I think I typed in ..". I can also pin-point, to day anyway, when I actually did something a few weeks or months back.

Some days I cover half a dozen pages with notes -- and those notes are extremely valuable. Without those notes I'd have to go ask some people questions that I asked them a month ago -- that's not professional, that's just plain dis-organized.

I've also heard that personal connections, or networking, actually produce 60-70% of jobs, and the web sites that you mentioned work about 1% of the time. I put more faith into a site like LinkedIn myself. I found my last two jobs through personal connections -- it works for me.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Replies are listed 'Best First'.
Re^2: Interview Counterattack: "Show me a project-plan"
by ww (Archbishop) on Apr 16, 2008 at 14:58 UTC
    Good points, talexb; especially re the log and personal connections.

    Two minor nits (which is, I suppose, redundant, but I call it "emphatic" with the emphasis on "minor"):

    • As I read the OP, the ref to M$ Project was more by way of example than a global requirement. (Heaven help us if it wasn't.)

    • And re your "But these days I can't believe that managers think they're going to get 50% more quality code done by getting their developers to work 50% longer hours."

      Certainly some -- perhaps even "most" -- managers have learned that lesson, but to paraphrase a famous observation, "Nobody ever went broke underestimating the managerial skills of some managers... but one may go broke by overestimating their willingness to buck their bosses."

    Certainly, some kind of "interview counterattack" to learn whether the manager is among the enlightened will have great value.

    Overall, though, a heartfelt "++"

      Regarding the MS Project reference, you're quite right -- although I detest this product, it's more because it's the embodiment of 'some guy wearing a suit, sitting in an office telling me what to do because of some damn chart'. When you get down to a GANTT chart that's down to the level of spending half a day writing one specific routine, that's the time to start a new career as a musician .. or something.

      Again, an opened ended question goes a long to probing gently about the employers attitude, in this case, towards developers doing overtime. The whole job interview thing is a conversation that's really a negotiation. You have to explore, question, examine, with the understanding that both sides want to get as much information from the other side as possible, so as to make a fully informed decision on whether This Is The One.

      Hearing someone describe a job interview as 'self-flagellation' tells me they're not comfortable in their own skin yet. Or maybe it's the jacket and tie -- hey, if you're not comfortable in it, ditch it and wear something comfortable. Think about it this way -- if you're going to wear a suit every day, then wear one to the interview. If not, not. I wore black jeans, nice shirt and sweater to my first interview at $work[-1] and I was probably the best-dressed in the room. I dressed down (ditched the sweater) for the second interview, and it was (as the kids say) all good.

      And thanks for the vote of confidence. ;)

      Alex / talexb / Toronto

      "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

        I was making a tongue-in-cheek simile, of course.

        One of my early co-workers once said to me, “you can never go wrong in a light-pinstripe blue suit with polished shoes.” I don't personally dress-up much like a page from Vanity Fair, but when he did, he was right.

work practices: log books, notes files (was Re^2: Interview Counterattack: "Show me a project-plan")
by doom (Deacon) on Apr 16, 2008 at 21:36 UTC