in reply to What I am paid for

In one sense, a good programmer should "own" her or his code: be responsible for it, and provide insight if needed. If someone calls you a year later and asks about something, you should do the courtesy of giving any short answer you can (and if a short answer isn't possible, you should at least offer to look at it again).

There are limits here too - if someone continually is calling and asking questions, at some point or another you'll have to gently insist that this is taking enough of your time that your consulting rates will need to start applying for further questions (but you'll answer this one). If you work for the same company, it might be time to get managers involved for your own protection and so that you have this to put on your review come next time...

Replies are listed 'Best First'.
Re^2: What I am paid for
by Anonymous Monk on Mar 12, 2010 at 01:35 UTC
    Um, no. Contact after the original contract, unless explicitly negotiated, is a time for renegotiation, not help.
[reply]
      I prefer to think of a little of this as paying forward: if I've helped establish a culture of helping, people who've worked with me will be more willing to reciprocate if I ask them for help.

      And "help" isn't always "I don't understand this code"; sometimes it's "Got any leads on a new contract?" or I need a job - could you put in a good word for me at X?". If you've established that you will do a favor, you're more likely to get a favor.

      Everyone's got their own call on this; this is mine, and it's worked for me. Yes, you do need to have limits. But you should also follow Wil Wheaton's advice.

[reply]

        I like your advice ++. However! I will never, never, never, never, never, never, never, never read a word the Jar Jar Binks of Star Trek has committed to the Void. And as your friend, I insist you desist.

[reply]

In Section Meditations