How I keep track of every job I've ever had (without journaling).

Most people don't update their resume until they need one. They scrape it together in an afternoon, two days before the application deadline, drinking the third coffee, trying to remember what their second job's title actually was. They Slack their old manager: "what year did I leave again?" They squint at LinkedIn. They guess. They submit it.

Then they make a private promise: next time, I'll keep better records. Next time, I'll start a career journal.

They never start a career journal.

Why "keep a career journal" never sticks

The productivity-influencer corner of the internet has been telling people to journal about their career for at least fifteen years. The advice is always the same: every Friday, write a paragraph about what you did this week, what you shipped, what you learned. Reflect. Capture the impact metrics. Quantify everything.

This is fine advice. Nobody does it.

The reason nobody does it isn't laziness. It's that journaling about work is, itself, a kind of work — and the people most likely to need a career journal (people with demanding jobs, people who actually shipped things this week) are exactly the people who don't have a free hour on Friday afternoon to sit down and curate their own career narrative.

The advice fails for the same reason "drink eight glasses of water a day" fails. It assumes a future version of you who is more disciplined and less tired than the current version. That person doesn't exist.

What works instead: maintain something that already needs to be current

The trick is to skip the journal entirely and put the data somewhere that is, for unrelated reasons, supposed to be up-to-date.

A resume PDF doesn't qualify. PDFs are a snapshot — you write one when you need one, then forget it for two years until the next time. There's no reason to open resume_v3_final.pdf on a quiet Tuesday and add a bullet.

A profile you can share with a link does qualify, because the link is in your bio, in a few application forms, occasionally on a slide. People are looking at it. The asymmetry between "what's there" and "what's true about you" is small and visible. When something changes, you notice. You update the page in three minutes.

That's the whole habit, dressed up. You're not journaling. You're keeping one document accurate. And accuracy, unlike journaling, has external pressure behind it — every time someone clicks the link, you have a small interest in what they see being correct.

The 60-second habit

Here is the entire system:

When something happens that is the kind of thing you would, in two years, wish you remembered — open your profile, add one sentence, save.

Not at the end of the week. Not at the end of the month. Right then. The moment is when you remember.

Examples of moments worth a sentence:

A project shipped. You worked on it for a month. Add a bullet under the relevant job: "Shipped X, the thing that does Y, used by Z."
You moved a metric. "Took customer onboarding from 11 minutes to 4 minutes; reduced first-week support tickets by 30%."
You learned a new tool. "Took on the first production deploy of [thing]."
You changed titles. Update the title.
You changed managers. Add the new manager's name to the description if it'll matter for references later.

Each one takes under a minute. Each one would take you twenty minutes to reconstruct in two years.

The trick is doing it right after the thing happened, when the impact metrics are still in your head, when you remember exactly what changed. Memory is a lossy compression algorithm. The longer you wait, the lossier the compression. Future-you will thank you for catching the data while it was still high-fidelity.

What this saves you when it's job-hunting time

Jobs end faster than you expect. Sometimes you choose to leave. Sometimes you don't. Sometimes the choice is gradual — a series of small disappointments — and sometimes it's a Tuesday afternoon Slack message.

Either way, you'll need to communicate what you did and why it mattered. Recruiters will ask. Interviewers will ask. The application form will have a free-text field labeled "describe a project you're proud of," and the cursor will blink while you try to remember.

If you've been keeping the profile current, this is a 5-minute exercise: open the page, copy the relevant lines, customize for the role. If you haven't, this is the same kind of evening you've had before — staring at the wall, asking yourself whether the project you led used Postgres or MySQL, asking your old manager for the dates.

Worse: in the version where you scramble, you forget things. You forget the project that didn't ship but taught you the most. You forget the time you covered for someone on leave and learned a whole new system. You forget the metric. You forget the recommendation a manager once mentioned over coffee. The PDF you generate in 24 hours under deadline is a thinner version of your career than the version you would have produced over years.

This isn't a productivity hack

The framing matters. "Productivity hack" implies that doing this earns you something — output, success, an edge. It doesn't. The reward is small and only collected later, when you need it.

This is more like flossing. Or reviewing your bank statements. Or backing up your laptop. The kind of small, low-glamor maintenance that the version of you who needs it most will find easiest to skip. The reward isn't compounding interest. The reward is showing up to a moment that matters with the data already on hand.

The link is at klypn.com. The 60 seconds is whenever something happens. That's the system.