The latest articles on DEV Community by nicolasborrazas (@nicolasborrazas). https://dev.to/nicolasborrazas https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3889117%2F68f50355-eccc-4a4f-9c41-68f8b52a782f.jpeg https://dev.to/nicolasborrazas en nicolasborrazas Mon, 20 Apr 2026 13:56:31 +0000 https://dev.to/nicolasborrazas/how-i-stopped-losing-4-hours-a-week-writing-client-status-updates-1ke3 https://dev.to/nicolasborrazas/how-i-stopped-losing-4-hours-a-week-writing-client-status-updates-1ke3 <p>The Context Switching Tax<br> As developers, our flow is sacred. But every Friday, I had to stop coding to perform "translation work" for my clients. They didn't care about "Refactored the auth middleware," they wanted to know "The login system is now more stable."</p> <p>The Solution<br> I built a pipeline that uses the GitHub API to fetch my activity and passes it through a structured prompt engine.</p> <p>Key Technical Challenges I faced:</p> <p>Context Mapping: I created a "Soul Map"—an initial index of the repo so the AI understands the project's domain before reading a single commit.</p> <p>Deep Code Analysis: Implementing a way to read diffs securely in-memory without persisting any source code.</p> <p>I turned this into a tool called commitplain. I’m curious: how do you guys keep your non-technical stakeholders in the loop without losing your mind?</p> <p>Check it out here: <a href="https://commitplain.com" rel="noopener noreferrer">https://commitplain.com</a></p> productivity career github webdev