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...

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.