work-log: Claude records everything

October 2025. Opening code I wrote in June. Don't understand why I did it that way.

No comments. Git commit message: "fix". Memory doesn't remember.

Solution

Using Claude for coding for a couple months now. Ask it to record all completed work.

Folder work-log. Each decision - a file.

work-log/
├── 2025-10-15_auth-refactoring.md
├── 2025-10-16_cache-strategy.md
├── 2025-10-17_api-versioning.md

What gets recorded

  • Problem: what wasn't working
  • Options: what I considered
  • Solution: what I chose and why
  • Code: key pieces

Not documentation for users. Documentation for me in a month.

How it works

Finish a task - ask to write to work-log. Claude creates a file with date and description. I check and move on.

Don't write worklogs myself. Don't spend time. But everything is documented.

Statistics

833 files in 2 months. A lot? That's 10-15 files per day. Claude writes fast.

Result

Open old code. Don't understand. Search in work-log. Read. Understand.

AI also helps better when there's context. Share relevant files - it understands why things were done that way.

← Back to blog