Sorry to disagree, but in my opinion: 1. and 2. are not "nice", not ethical, and maybe against the law. If that turns up you may be even fired saying that you caused serious damage to the company putting bugs to the code intentionally or not helping her to solve the problem even when you knew how to solve it. She's in the stable position. You do not know why she's the favourite, it could be because she has better communication skills, maybe because she has something in common with him (sexual or other relationship). 3: Only proves that once you touched the source code "all you done is to stamping it" - and as the black sheep you'll be cut off first... 4. I think this is the best. When you have a chance you can talk to manager informally, like "How did you like my new project? I was working alone on this really hard and it is like my baby, so do you think this or that blah blah blah". Tell him then, that you want to do the first version as well as you can see that as a prototype person your name is not going to disappear on the project even though you wrote the whole lot. But again, don't blame her that she stolen your hard work, say that you know that "you know it is the company policy" ... and let your manager wonder if that's really the policy or not - if not you might win, if yes, you may can ask to change position/responsibility within the company. If gentle communication does not help you may try to tell in front of everybody, that's unfair not seeing your name but someone else even though you have 90% of work and the one with her name has only 10%. And ask in front of everybody that how the management thinking about this problem. This may can be very bad as no manager likes to be confronted in front of everybody, so it has only a 50-50 chance plus you could get a bad mark as well but as a last resort... anyway, you can find a better job, but before that make sure that you've tried.... 5. Never works... for such a person she will always manage to do it somehow, hiring a new engineer, or I do not know how but the do survive, while you always running away and will be looser for your rest of your life because there are such people everywhere. GOTO 4. :-) Tamas On 1/16/08, alan smith wrote: > > 1. plant a bug that only happens when specific things happen....hard to > repeat, but its there. Pretty obvious she can't fix it but you can....might > expose her for what she is since you can fix it. > > 2. Easter egg...same as above. > > 3. Hide your name in there somewhere as the original author > > 4. Show all your development work to the manager...confront.... > > 5. Find a new job...leave here sitting alone and not able to > product...she gets fired, you get hired back as a overpaid consultant to do > the same job. > > Andre Abelian wrote: > Hi to all, > > At work I do Hardware, Software, Layout. The way we setup is > I work on new project "never done" I put > together schematic, layout, Software and then deal with customers when > finally > it is done the project goes to production department. There is a Russian > lady > takes my code changes about 1-2 % and she removes my name as first version > and she puts her name on it. This is my 3-th project she is doing it. For > some > reason she has extremely good relationship with her manager. Knowledge > wise > she is very bad. My question is: Removing original person's name as > prototype version > is this expectable? Today every thing is paper work. Based on paper work I > didn't > work on the software and she is using 95% of my own routines etc. Any > suggestion ? > > > Andre > > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > > > > --------------------------------- > Never miss a thing. Make Yahoo your homepage. > -- > 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