Can you let us know how you get on? RP On 17/01/2008, Andre Abelian wrote: > I just wanted to thank all of you for excellent suggestions and comments. > If you see me outside walking and talking to myself then it means > no thing changed. "just joking" > I will see what I can do about it. > > thanks again > > Andre > > > > -----Original Message----- > From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu]On Behalf > Of M. Adam Davis > Sent: Wednesday, January 16, 2008 11:49 AM > To: Microcontroller discussion list - Public. > Subject: Re: [OT]:Software related question > > > These two responses are essentially how I'd approach it, with some > comments afterword: > > On 1/16/08, Paul Hutchinson wrote: > > I would definitely talk to your manager about this from a > > standards compliance standpoint. > > On 1/16/08, Eoin Ross wrote: > > My thinking is that there should be a revision > > history/list/file/comment that shows EVERYONES name, > > date, and details of what was done. > > I don't know the industry you are in, but TRACEABILITY and STANDARDS > are key here. > > First, I'd assume that the code belongs to the company, and that the > person in question is acting according to company policy. Don't talk > to anyone with the assumption that she's doing somethign wrong, or > taking 'credit' for 'your work'. This isn't your work - this is > output you've exchanged for cash, and the company can do with it as it > pleases. > > With that out of the way... > > I'd strike up a simple and quick conversation with my boss, something > to the tune of, > > "[boss's name], I've noticed that when my source code is added to the > production system (or whenever in the process the changes occur) that > the comments containing traceability information, such as names, > dates, code affected, is edited or removed. I'm concerned that with > this information gone, among other things, code maintenance would be > more difficult, and traceability is lost. > > I'm curious about the company policy behind this, and whether I am > still responsible for code that does not have my notes and comments." > > Then listen. Don't talk about who does the changes, just talk about > the effect and impact, and avoid making it sound as though you deserve > 'credit'. > > Eventually, through conversation, they will either have to admit they > don't want/need/have traceability, or that the process that's been > occuring is not within company policy. > > But my suspicion is that things will keep going on as they have been, > and your best bet is to book it out of there as soon as reasonable. > > If, however, you are a contract programmer, then it's possible that > the person who changes your code a little bit, then drops their name > on top while removing yours is simply following company procedure. As > a contract programmer you will not be available for future > maintenance, and some companies (oddly) demand that an employee take > responsibility for the code completely, and they enforce it by > removing references to the original contract programmer so the > employee can't fall back on, "Well shoot, it's what's his name's > fault!". It's silly in one respect - there's no guarantee that > employee will be around either. > > At any rate, don't take it personally - it's just a job. > > -Adam > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist