Hopping is useful. If you are underpaid, stuck, or working somewhere toxic, leave. A company or team does not get loyalty by default. It is earned both ways.
But there is a cost to treating every new logo as growth: you leave before some of the best parts of work arrive.
Context becomes judgment. You stop seeing a system as tickets and diagrams. You remember the approach that failed, the incident it caused, and the constraint everyone now calls “weird.” You get to watch your own decisions come back. Sometimes that is humbling as hell. It is also how you learn.
You also build long-lasting relationships. That is gratifying in its own right, but it changes the work too. When your team needs something, going the extra mile feels less like performative heroics and more like showing up for people whose trust you have earned.
That trust becomes agency. People stop handing you tidy work and start bringing you the ambiguous problem—the thing with no obvious owner, where the answer matters after this quarter. Not because you have a grander title. Because they have seen how you work when things are messy.
Recently, I read Sunil Pai’s The Senior Engineer Death Spiral. His distinction between an outcome-based and a momentum-based mindset stuck with me. Big work rarely arrives through one heroic push. It comes from slow, useful, reliable work—and from relationships strong enough to keep that work moving when things get hard.
None of this means staying forever. A long stay is only valuable if the pay is fair, the problems still grow, and the people make you better. If those things disappear, “compounding” can become a flattering word for inertia.
But I no longer think a new logo is automatically progress. Sometimes the ambitious move is finding a place worth building in—and staying long enough to be wrong, learn from it, and become useful in ways that a résumé cannot measure.
