https://blog.abhipraya.dev/tags/developer-experience/Recent content in Developer-Experience on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaThu, 12 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-a/teamwork-tools/Thu, 12 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-a/teamwork-tools/<h2 id="why-tooling-is-a-team-problem-not-a-devops-problem"> <a class="anchor" href="#why-tooling-is-a-team-problem-not-a-devops-problem" data-anchor="why-tooling-is-a-team-problem-not-a-devops-problem" aria-hidden="true">#</a> Why Tooling Is a Team Problem, Not a DevOps Problem </h2> <p>Most university software engineering courses teach you <em>which</em> tools to use (Git for version control, Jira for tickets, Docker for deployment). What they rarely teach is <strong>how tools interact with each other</strong>, and what happens when they don&rsquo;t.</p> <p>In a professional environment, a single commit can trigger a cascade: CI runs tests, a Slack bot notifies the team, a coverage report lands in SonarQube, and the ticket moves to &ldquo;In Review&rdquo; on the project board. This doesn&rsquo;t happen by accident. Someone has to build that integration layer, and in a university team, that someone is usually whoever cares enough about developer experience to do it.</p>