This was my experience at a previous company. As it was a small startup company, some of the normal software development procedures were not followed strictly. One of my colleagues was a senior programmer with the company for 2 years. His skills were quite lacking. He would allocate his tasks to me and then take credit for the work himself. He did this regularly, while I would also have to finish my own tasks.

I felt that I couldn't express this situation to senior management as that colleague had their trust.

Later, I tried to delay his tasks assigned to me so that reflect poorly on him (as he couldn't finish tasks) Also, client complaints piled up unresolved issues. Now the company knows about him.

Actually, now I'm heading to a new company as a Lead. Now I'm completely free with these situation.

Have any of you experienced situations like this? What would/did you do?

  • 9
    I do not understand your rationale for why you cannot tell senior management about this.
    – user1249
    Commented Apr 2, 2011 at 11:58
  • 5
    That colleague has seems to have some friendships with one of management members - saying no one will accept if any complaint is accused of him(indirectly when one of colleague tried to complaint about him) Commented Apr 2, 2011 at 12:00
  • 4
    Can't you commit the changes to source control yourself?
    – TZHX
    Commented Apr 2, 2011 at 12:06
  • 7
    This sounds the like the story from the original Tron movie.. Commented Apr 2, 2011 at 12:25
  • 9
    Managers are often credit vampires, that's how they became managers. It's a fact of life, just like unicorns and werewolves.
    – user131
    Commented Apr 2, 2011 at 17:02

4 Answers 4


You already did what I think many would have advised, which is to leave the company and find new management.

Had you stayed, source control would be one way to build evidence. The other would have been to not finish his tasks, which it sounds like did happen. At some point management (well, competent management anyway) would naturally want to take a peek at what was going on. You'd have an audience then, and if you'd documented what you did on your tasks and could produce the emails or other information showing the additional tasks the lead gave you, it would have been pretty obvious your workload was not just your own.

Finally, my understanding is that what you've described happens in many places. Professors take credit for grad student work, coaches get credit for an athlete's work, and company heads reward themselves handsomely for work done by legions of others. Students take credit for the work of purchased research or cheat sheets. Your situation seemed more personal and understandably frustrating, but it sounds like you already did the best thing you could and moved on.

  • Thank s - i feel whatever nothing gonna change - so i left the company & Now everything moving Fine! Commented Apr 2, 2011 at 13:08
  • +1 One note though: lead != senior. Part of a lead's job is to delegate some tasks to the team. That said, stealing credit for the actual work is not. Commented Apr 2, 2011 at 21:14

I would say there's nothing you can do, once it has happened, unless you have evidence. And it sounds like you've come out of the situation ok.

I would suggest that this kind of thing is pretty uncommon but certainly not unheard of in the industry, so I would take a lesson from this and protect yourself in future.

The best line of defence is source control. If you're in a company who doesn't use source control then just install Subversion and commit the code to it, then suggest everyone should use it. There is never a good argument not to.

  • you are correct, now there are using SVN! Commented Apr 2, 2011 at 12:31
  • 1
    Tell them to use git, then :-)
    – Joey Adams
    Commented Apr 2, 2011 at 20:54

I would say no to the next task and if he wants to discuss it with his friend the supervisor then the supervisor can tell me to do the senior developer's work. So in a way, you will get credit for it.

I do want to point out that I think this is different with managers. I worked with a team that would complain if a manager took credit for something they did. I just didn't get the rationale that the manager should list everyone who works on every little ad hoc project. The manager handled the team well. Looked out for our interests (Pushed upper management to get me hired in time to take advantage of 401K plan.). Set up a training schedule. Constantly told us to get out of the office if we were working too many hours. My thinking is to do what you can to get your manager promoted. Good ones will reward you. It makes the team look better in the eyes of the rest of the company. Most people get promoted because the person above them was promoted and not because they were fired for incompetence (And if that's the case you can be guilty by association and deemed unfit as well.).

  • You are right - as a startup company they have some kind of intensions to have senior members in office for product movement/progress in the sense - which created a situation where not to take any measures on specific person whoever like this! Commented Apr 2, 2011 at 13:23
  • 1
    A good manager in a good company will give credit publicly where its due and take the blame and pass it down privately. Any credit to their staff will reflect well on them anyway. Unfortunately, too many companies discourage that kind of thinking in any number of ways.
    – pdr
    Commented Apr 2, 2011 at 13:48
  • @pdr - as long as everyone doesn't expect some type of itemized acknowledgement. Never giving credit is a bad thing. Companies that try too hard to find blame zap too much energy for anyone to give compliments.
    – JeffO
    Commented Apr 2, 2011 at 19:10

No, I never experienced that situation. Even early on where I didn't use source control, no one ever tried to get credit for my work.

If I had, I would talk to the person or senior management.

Can you sign your code?

If you can't take credit for your work, what do you think your options are?

Not the answer you're looking for? Browse other questions tagged or ask your own question.