I've stepped in and fixed code which wasn't under my control. Sometimes things just need to be done, and can't wait until Monday morning, or to whenever it is that the responsible person returns from a trip.

Example: a few years ago for a project we doing, I had to modify about 150 tables in a database, create or modify 3 triggers on each of those tables, and create a stored procedure and an index for each of those tables. That meant about 450 modified or new files, and 900 new or modified database objects. More than 50,000 lines of SQL, all generated by a Perl script.

It was going to be the biggest bulk submit we had done so far, and there was no way of doing this cleanly during the week when dozens of other developers would be submitting stuff.

So, I had claimed exclusive use of the development area during a Saturday. Late in the evening the submission process failed. Because of bugs in the submission software (a Perl/Tk program, maintained by a totally incompetent programmer). I could do two things, either wait till Monday and let the programmer in charge try to fix it. That would mean I had to delay the submission process till the next week - causing havoc on whatever day I was going to submit. Or attempt to fix the problem myself. I chose the latter. It turned out that I didn't completely fix the problem (because the author was a great believer in "cut-and-paste" and I hadn't found all the copies of the same piece of buggy code), but at least I could submit my stuff.

Did I leave a long note to the programmer what I had done and why? Hell no. I emailed his supervisor (which was formally my supervisor as well, but I usually ignored him and dealt directly with his boss) saying I had fixed the buggy software, cc-ing the programmer.

If you are working in a company, don't assume ownership of code. It isn't yours - it's the companies. Others will fix and break things. Only if you are available 24x365 you might have a chance of exclusively working on the code. It's nice, and most of the times useful, to email the person responsible if you did change things. But it's immature to expect noone else to touch your code, or to be notified. Be your own boss if you can't stand it.

Abigail

In reply to Re: Has this happened to you? by Abigail-II
in thread Has this happened to you? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.