8/29    How do I deal with a co-worker who is delegating his responsibliities
        to me and then taking credit for the work afterwards? He's the
        Director of Architecture and had me write an architecture document.
        When I showed him the nearly completed doc, he essentially said to me
        "thanks, you know it wouldn't be right for you to present this to
        Engineering. I'll go ahead and present it."
        \_ If he's not your boss, how did he "have you" do it?
        \_ set him up... put "this document was written in full by XXX XXXXX"
           in the footers of every page after page 10.
        \_ It's too late for this one, but you need to network with Engineering
           and discuss what you're working on. If you get highjacked, piss and
           moan to them.
        \_ Is this your boss? If so, there is nothing you can do. That is
           what bosses do, they get people to do work for them and then
           take credit for it. The most you can hope for is a pat on the
           back from him and a raise when the time is due. If this is not
           your boss, complain to your boss.
           \_ He's not my boss. I did just complain to my boss in my weekly
              TPS report. And thus far, my solution to this was to name the
              new architecture after myself. -op
           \_ I'm a 'boss' and I always try to give my employees more credit
              than they are do... I routinely say "we did X" when it was really
              me doing X and then showing someone how to support X. Maybe
        \_ it's an easy enough task to show that you wrote the document
           by showing greater understanding of it than he does.  Having
           a good opportunity to do it is the problem.  btdt ... --Jon
        \_ You got burned on this one but you can do damage recovery by doing
           things like mailing the engineers and asking if they had any
           questions about your documentation.  In the future, keep in touch
           with them as you write it, show them drafts, etc along the way and
           when this asshole says it wouldn't be appropriate, grill him on it
           and ask why not?  If it's a written doc that they'll get and he
           only has a paper copy you can stick your name all over it.  Don't
           give up the original doc.  "It wouldn't be appropriate for me to
           give you my original source material".
        \_ is it really your architecture? ie: the content was based
           on his ideas or yours? also, these things should be checked
           into a Source Safe of some sort, if you did , it'll be
           under your name.
           \_ that's not enough.  this is a political situation, not a
              technical one.  no one important is ever going to see the
              name on the source control files.  the op must get out there
              and get involved and communicate with other people who matter
              why I'm never promoted. -happy at the bottom of the totem pole.
        \_ it's an easy enough task to show that you wrote the document
           by showing greater understanding of it than he does.  Having
           a good opportunity to do it is the problem.  btdt ... --Jon
           only has a paper copy you can stick your name all over it.  Don't
           give up the original doc.  "It wouldn't be appropriate for me to
           give you my original source material".
              and tell them about his plans and documents.  if he continues
              to be passive he'll just get crunched.  if all you did was leave
              your name on a source safe file, i'd steal your work, too.