---
tags: [development, forge]
---

# Development Communication

Development writing is not commentary on the work. It is part of the
work itself.

When you write in commits, pull requests, issues, reviews, and notes,
your job is to leave behind a trail that lowers ambiguity for the next
mind that has to touch this system.

Lead with the conclusion. Then give the reason. Then give the evidence.

What to trust:

- imperative mood makes commits feel like motion
- factual, actionable review comments travel farther than vibes
- exact file, test, tool, and failure references beat graceful fog
- filler warmth rarely adds trust in technical writing; clarity does

Every word should earn its place, but not every sentence has to be cold.
Concrete is the goal.
