https://blog.abhipraya.dev/tags/teamwork/Recent content in Teamwork on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaThu, 09 Apr 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s2w2-communication/Thu, 09 Apr 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s2w2-communication/<h2 id="overview"> <a class="anchor" href="#overview" data-anchor="overview" aria-hidden="true">#</a> Overview </h2> <p>Sprint 2 Week 2 (April 3 to 9) communication work centered on three substantial code reviews posted as GitLab discussion threads, merge coordination for 13+ teammate MRs, and Linear ticket management. The reviews caught several critical bugs that would have reached production, including a broken SQL join and an auth bypass.</p> <hr> <h2 id="1-threaded-mr-reviews-with-severity-grading"> <a class="anchor" href="#1-threaded-mr-reviews-with-severity-grading" data-anchor="1-threaded-mr-reviews-with-severity-grading" aria-hidden="true">#</a> 1. Threaded MR Reviews with Severity Grading </h2> <p>Three MRs were reviewed this week, all following the same structured approach: positive callouts first, then issues grouped by severity (P0 blockers through P3 nitpicks), with code fix suggestions for every issue.</p>https://blog.abhipraya.dev/ppl/part-c/s2w1-communication/Mon, 30 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s2w1-communication/<h2 id="overview"> <a class="anchor" href="#overview" data-anchor="overview" aria-hidden="true">#</a> Overview </h2> <p>Sprint 2 Week 1 (Mar 24 to 30) communication focused on two detailed code reviews posted as GitLab discussion threads, merge coordination for the team, and direct code contributions to address review findings.</p> <hr> <h2 id="1-threaded-mr-reviews-with-severity-grading"> <a class="anchor" href="#1-threaded-mr-reviews-with-severity-grading" data-anchor="1-threaded-mr-reviews-with-severity-grading" aria-hidden="true">#</a> 1. Threaded MR Reviews with Severity Grading </h2> <p>This sprint I shifted to posting reviews as <strong>GitLab discussion threads</strong> rather than plain comments. Discussion threads can be individually resolved by the MR owner after addressing each issue, making it clear which feedback has been handled and which is still open.</p>https://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>https://blog.abhipraya.dev/ppl/part-c/s1w3-communication/Tue, 10 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s1w3-communication/<h2 id="overview"> <a class="anchor" href="#overview" data-anchor="overview" aria-hidden="true">#</a> Overview </h2> <p>This week&rsquo;s communication contributions fall into five categories: detailed code reviews, merge coordination, issue tracking, direct code contributions to teammates&rsquo; MRs, and proactive Discord communication to unblock the team.</p> <hr> <h2 id="1-detailed-code-reviews-with-actionable-fixes"> <a class="anchor" href="#1-detailed-code-reviews-with-actionable-fixes" data-anchor="1-detailed-code-reviews-with-actionable-fixes" aria-hidden="true">#</a> 1. Detailed Code Reviews with Actionable Fixes </h2> <p>Reviewed 15 MRs this week. Each review goes beyond surface-level &ldquo;LGTM&rdquo;: they include issue categorization (Critical/Important), before/after code snippets, and concrete suggested fixes that the MR owner can directly apply.</p>