Developers often view documenting their work as bragging, but this article reframes it as essential collaboration. The piece argues that managers lack mind-reading abilities and cannot remember every pull request or 2am fix across multiple team members. Without clear records, they rely on flawed memory and recent events, creating a recency bias that undervalues earlier contributions.

The core issue isn't arrogance—it's providing managers with the evidence needed for salary, promotion, and bonus negotiations. When a manager can cite specific impacts like 'reduced transaction latency by 40%' instead of vague praise, their advocacy becomes far more persuasive. Documentation transforms subjective opinions into objective data that supports fair compensation.

The article suggests practical methods: keep factual records focused on impact, not effort, and share updates regularly in 1:1s rather than scrambling before reviews. Tools like BragDoc can automate this by extracting achievements from GitHub commits. This approach turns individual discomfort into systemic fairness, giving managers the ammunition to fight for their teams effectively.