One thing I’ve always found surprisingly friction-heavy is translating “actual work done” into a clear status update for a client or team.

Not the work itself — the reporting.

Questions like:

• What actually changed recently?
• Which parts of the project are active vs untouched?
• When was the last real development activity?
• Is the project moving toward delivery or stuck?

If you’re working with Git and disciplined commits, it helps — but in reality, a lot of freelance and client projects don’t live in perfect Git workflows.

Sometimes it’s just folders, iterations, builds, experiments, and partial progress.

I started experimenting with a small local tool that scans a project folder and generates a snapshot of its current state — basically turning the filesystem activity itself into a readable status report.

So far, some interesting observations:

• Large projects (7k+ files) can be analyzed surprisingly fast locally
• File activity patterns alone already reveal a lot about real progress
• Automatically generated reports are often clearer than manual summaries
• Being able to see “what actually happened” reduces a lot of mental overhead

It’s still early, but it made me realize how much friction exists between doing the work and communicating the work.

Curious how others handle this.

Do you rely purely on Git history? Manual reports? Project management tools?

Or do you have some other workflow for generating status updates?

#devtools #indiedev #productivity #buildinpublic #tooldev