search email community favorite this article chev-right latest posts article list comments tags video article login twitter facebook menu pinterest whatsapp

Employee gets exposed for taking credit for coworker's software work after he is forced to admit he doesn't know how to fix a system bug: ‘He had no idea where to even begin’

Advertisement
  • 01
    Cheezburger Image 10480765440
  • Advertisement
  • 02

    "My co-worker loves taking credit for other people’s work. Then he got exposed"

    I work as a software engineer and in my team we follow the usual process of writing code, reviewing it, testing it, and deploying it.
  • 03
    One of my co-workers, Steve, had a habit of taking credit for other people's work in front of management. He isn't a bad developer, but he loves making it seem like he
  • 04
    was doing more than he actually was. I'm quite introverted, so I don't usually speak up in meetings unless I have to. Calling someone out directly doesn't come
  • Advertisement
  • 05
    naturally to me, so I usually just let things slide. During a big project, I spent days fixing a complicated bug. The problem ran deep, and the fix had to work
  • 06
    across different parts of the code. If you hadn't actually worked on it, it was pretty hard to follow. After a lot of testing, I finally got it done.
  • Advertisement
  • 07
    At the next team meeting, before I could even say a word, Steve jumped in and started explaining my fix as if it was his. He kept saying
  • 08
    things like "We decided to... and "Our approach was to... making it sound like he was the person behind it. I was annoyed, but I kept quiet.
  • Advertisement
  • 09
    The next day, another bug popped up in the same area of the code. Our manager turned to Steve and said, "Since you worked on this, can you patch it?"
  • 10
    And that's when the fun started. Steve froze. The thing is, if you didn't actually write the fix, it wasn't easy to understand how it all fit
  • 11
    together. He had no idea where to even begin. He tried stalling and even sent me a message asking if I could explain the logic of the code real quick. I told him that I
  • Advertisement
  • 12
    was busy at the moment and that I will catch up with him later on. I didn't. After five hours of struggling, he finally admitted in the team chat and wrote something like
  • 13
    "Actually, I didn't write this part, maybe OP can take a look?" I replied, "Of course, I'll check it."
  • 14
    Ten minutes later, I had it fixed. Our manager came over and congratulated me. We were chatting for a bit and before heading off he made a
  • Advertisement
  • 15
    deliberate comment about how great it was having someone who actually understands what we are working on. Steve didn't say a word f you Steve.
  • 16
    render() { return React.Fragment <div className="py-5"> <div className="container"> <Title name="our" title= "product <div className="row"> <ProductConsumer> {(value) => { console.log(value) }} </ProductConsumer> </div> </div> </div> </React.Fragments
  • 17
    InnocentlyInnocent OP needs to be able to stand up for himself. If there wasn't another bug, Steve would've gotten away with it unscathed.
  • Advertisement
  • 18
    ehtio OP I know. It's just hard for me. I come from being. a pastry chef (almost 9 years) but I decided to study and became a software engineer. I guess I feel like an impostor sometimes.
  • 19
    Intelligent_Bad6942 Dude you just proved yourself. You're no imposter. You got this.
  • 20
    island-breeze As a people pleaser myself, one cannot oversea the fact that you did stood up for yourself in the best way possible. You may be shy, but you're growing a back bone. Well done.
  • Advertisement
  • 21
    ehtio OP I hope so. The thing is that the older I get, the more I notice that happening to others too, and I cannot stand it so I try to do better to also help others. So that helps.
  • 22
    CoderJoe1 Steve should leave people the credit they're due
  • 23
    Satori Namast3 Unfortunately faking it till you make it doesn't work with code. You either know or don't.
  • Advertisement
  • 24
    CatlessBoyMom Steve really should be in sales. Taking credit for how well something is done, without actually doing it, is kinda their job description.
  • 25
    blueavole Start speaking up. I worked on that Steve, can you define your contribution so we aren't doubling up? No more of this we shik

Tags

Scroll Down For The Next Article
Show Comments
Next Article