SCENE_01
Her slide deck, your week
You’re in the room when she opens the deck and walks through the feature like it arrived fully formed. The flow is clean, the bugs are gone, and the questions sound easy because you already solved the hard parts. Then the thought lands: She demos what I built and gets the credit. What she shows is the surface. What you remember is the late-night fixes, the invisible handoffs, the parts that only looked simple because you made them stable.
SCENE_02
The part that turns to bitterness
The private meaning arrives fast: if the demo gets praise, the work itself must not have counted. So you go quiet. You stop offering context in reviews, trim your notes to the bare minimum, and leave the maintenance trail unnamed. Sometimes you even imagine a visible failure, just so the room has to see what held everything together. The cost is that your own work becomes harder to point to, even for you.
SCENE_03
Treat the demo as a routing problem
A cleaner reading is less flattering but more useful: the credit followed the presentation, not the labor. That’s a visibility problem, not a value verdict. You can route attention without a confrontation by naming the backbone in your own record. Write down the systems, fixes, or decisions you carried, then make them readable before the next review or handoff. The work was real before it was visible.