Chaos and Order

💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

What a Move Solves and What Follows You
What Compounds Only If You Stay
What Goes Missing When You Are Always in Year One
Five Things to Check Before You Leave
A Decision to Stay Versus Drift
One Thing You Can Do Today
Where This Advice Does Not Apply
Further Reading

What a Move Solves and What Follows You

Changing jobs is not a cure-all, but it is not powerless either. Some problems it genuinely resolves: the product stopped growing, there is nobody here to learn from, the size of problem you want to work on does not exist at this company. These are caused by the environment, so changing the environment actually removes them.

Other problems follow you. The habit of not defining your own scope, the tendency to postpone conflict, the cycle of boredom that arrives once novelty wears off — these travel in your luggage. So the first question is not about the company but about where the cause lives. Is what is hard right now confined to this building, or does it walk around with me?

The way to tell them apart is to look backwards. Check whether the same kind of frustration existed at your previous organization. On the second repetition it is hard to put much weight on the environment. Conversely, if it is the first time you have met this problem and three or more people explain its cause the same way, that is structure, not personality. Skip this test and you will be writing the same sentences again six months into the new company.

What Compounds Only If You Stay

Some things reset on a move and accumulate if you stay. The first is trust: how quickly your words get through, whether people give your proposal a hearing before judging it, is a balance built by time. The second is second-order knowledge — why the system came to look this way, which decision came out of which constraint. None of it is written in the code. The third is standing to take on big work; organizations generally do not hand a risky project to someone who just arrived.

The fourth is the most expensive. It is the experience of receiving back the consequences of your own decisions. Someone who has personally lived with the maintenance cost that a structure they chose two years ago now produces develops judgment differently from someone who left before each of those moments arrived. You cannot buy that stretch from a book or from another company.

What Goes Missing When You Are Always in Year One

Repeated short tenures sharpen only the skills of the opening stretch. Finishing onboarding fast, reading an unfamiliar codebase, making a first impression — those genuinely improve. But maintenance and long-run outcomes are absent from that list. Living with a system for a long time, seeing the third year of something you built: those stay empty.

The gap does not show on a resume; it shows in judgment at senior level and beyond. How tenure itself is read differs by market, by industry, and by period. In some markets frequent moves read as an ordinary path, and in others they still invite an explanation. So the concern here is not other people's evaluation but the actual capability gap that a repeated first year creates.

Five Things to Check Before You Leave

What you have not yet tried by staying. Have you renegotiated the role, asked for a team transfer, proposed a project? Moving teams is often cheaper than moving companies.
Whether the other side is the same problem in a different version. Write the reason it is hard in three lines, then answer how those three lines differ at the new organization. If no answer comes, you still lack information.
The finishing point of your current work. Leave before the outcome lands and the work never becomes a line on your resume.
Relationships. The industry is small, and the reference you need in a few years is manufactured in your final two weeks.
Financial cushion. With no cushion there is no negotiation. Much of the leverage discussed in the next part comes from here.

A Decision to Stay Versus Drift

Staying is also a decision. One property separates a decision from drift: whether a deadline and a condition are attached. "Let me just stay a bit longer" is drift. "I will see the outcome of this project through next quarter, and if my role has not changed by then, I re-open the question" is a decision.

Writing the condition down improves two things. The mental cost of weighing it every day disappears, and when the review date arrives you judge from a record instead of a mood. Memory otherwise mistakes the feeling of the last week for a summary of the entire period.

One Thing You Can Do Today

Write your current decision as one sentence with a date attached. "I stay until [date]. If [what] happens by then I keep staying; if [what] does not happen, I move." If the sentence feels awkward to write, it usually means you have not yet worked out what belongs in the condition slot. That working out is the actual body of this task.

Where This Advice Does Not Apply

Some situations make the compounding calculation meaningless: harassment, an intensity that is eating your health, an unsafe environment, a request you cannot ethically accept. In those cases the attempt to calculate what staying earns is itself harmful. Leaving quickly is right, and the decision needs no further justification.

Caution also becomes costly when the company's survival is in question. If several signals overlap and you wait, you end up moving at the same time and for the same reason as everyone else. And this post assumes a situation in which you can choose where to go. With only one option, the problem of judgment turns into a problem of management.