We’ve all been there.

Performance review season arrives, or you finally sit down to update your resume, and suddenly your brain goes blank.

You know you worked hard.

You know you shipped useful things.

You know you helped the team.

But the details are gone.

The refactor from seven months ago. The incident you prevented. The teammate you unblocked. The awkward technical decision that saved the project later.

That is the problem I’m building careercraft.ing around.

I’m a big believer in brag docs, the approach popularized by Julia Evans. But I also know why most of us stop maintaining them: the manual work is too easy to postpone until it is already too late.

careercraft.ing is a private career vault for software engineers.

It helps you capture meaningful work while the context is still fresh, then turn those raw notes into clearer evidence for self-reviews, promotion packets, resumes, interviews, and salary conversations.

The important part: it is built for the way developers already work.

Instead of opening another empty document and trying to remember everything from scratch, you can capture wins from tools like Claude Desktop, Cursor, or any MCP-compatible client.

You decide when something is worth saving.

No background monitoring.

No employer-owned performance file.

No surveillance-style tracking.

Just a faster way to preserve the work that usually disappears before review season.

What careercraft.ing helps with:

• capture wins before memory fade turns them vague

• turn raw notes into review-ready evidence

• document invisible work like mentoring, unblocking, reliability work, and process improvements

• prepare stronger self-reviews, promotion packets, resumes, and interview stories

• keep a portable career record that belongs to you

I’m building this because “just work hard and hope people notice” is not a career strategy.

The work still matters.

But if you cannot remember it, explain it, or prove it when the moment comes, it is too easy for that work to disappear.

I’m building careercraft.ing because I don’t think good engineering work should disappear just because we forgot to document it.

If you’ve ever panic-written a self-review from memory, this is for you.