The advice is everywhere and it's correct: keep a brag document — a running list of what you accomplished, so performance reviews and promotion cases are built on facts instead of vibes. Julia Evans wrote the canonical argument for it years ago, and nobody has seriously disagreed since.
And yet almost nobody keeps one. The failure mode is always the same: you create a beautiful template in January, and in November it contains three bullets from the first week. Not because you did nothing — because updating a separate document about work is itself work, the first thing dropped in a busy week. A month later the context is gone: who pushed back, what the number was, why it was hard. Memory doesn't keep receipts.
Flip it: don't write the document, log the days
The fix is to stop treating the brag document as a document you maintain, and start treating it as a query over a log you were keeping anyway. Three habits, all tiny:
- Two lines a day, on the day. What you shipped, unblocked or decided — written in today's note while you still remember the details. If you already keep an interstitial log, you're doing this.
- Mark the wins as they happen. When something is brag-worthy — shipped the migration, fixed the incident, got the thank-you email — put a
#winon the line. It costs one word and zero decisions. - Compile on demand. When review season arrives, pull every
#winfrom the last six months, paste the list into the template, and spend your energy on the narrative instead of the excavation.
What this looks like in practice
In Hejour, every day is already a page, so the log has nowhere else to be. A #win anywhere in a day's note becomes a thread: press ⌘P, type #win, and there they are — every win, on its date, newest first. The brag document assembles itself out of days you already wrote.
The same log quietly answers the smaller versions of the question too: standup (“what did I do yesterday?” — it's the top of yesterday's page), the monthly status update, the “what did we decide in March?” thread. One habit, four payoffs. It's the same mechanism that makes a developer journal work — the brag document is just its most career-shaped output.
Two lines today, a tag on the good ones. Hejour is a free download, and November-you will read those lines like a fan letter.