https://blog.abhipraya.dev/tags/python/Recent content in Python on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaFri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w3-programming/Fri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w3-programming/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>This week&rsquo;s invoice management feature (MR !12) required a full CRUD stack with filtering, sorting, auth enforcement, and business validation (status transitions, admin-only delete). Building this properly meant enforcing strict layer boundaries and handling the tension between HTTP concerns and domain logic.</p> <h2 id="the-three-layer-pattern-in-practice"> <a class="anchor" href="#the-three-layer-pattern-in-practice" data-anchor="the-three-layer-pattern-in-practice" aria-hidden="true">#</a> The Three-Layer Pattern in Practice </h2> <p>SIRA&rsquo;s backend follows Router → Service → DB, where each layer has a single responsibility:</p>https://blog.abhipraya.dev/ppl/part-b/s1w3-tdd/Fri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w3-tdd/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>This week shipped three full-stack features using strict TDD discipline: invoice management (CRUD + filtering), layout/dashboard (sidebar, header, dashboard with role-based navigation), and a payments sidebar navigation link. Each feature followed red-green-refactor with tagged commits.</p> <p>The project now has <strong>392 backend tests</strong> and <strong>195 frontend tests</strong> (587 total), up from 51 last week.</p> <h2 id="red-green-refactor-commit-discipline"> <a class="anchor" href="#red-green-refactor-commit-discipline" data-anchor="red-green-refactor-commit-discipline" aria-hidden="true">#</a> Red-Green-Refactor Commit Discipline </h2> <p>Every feature branch this week followed tagged commits so the TDD flow is auditable from the git history alone.</p>https://blog.abhipraya.dev/ppl/part-b/s1w2-tdd/Wed, 04 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w2-tdd/<p>TDD forces you to think about the interface before the implementation. This post covers how it was applied in the Smart Invoice Reminder AI (SIRA) backend for Sprint 1.</p> <h2 id="test-distribution"> <a class="anchor" href="#test-distribution" data-anchor="test-distribution" aria-hidden="true">#</a> Test Distribution </h2> <p>The API currently has 51 test functions across 4 files:</p> <table> <thead> <tr> <th>File</th> <th>Tests</th> <th>Scope</th> </tr> </thead> <tbody> <tr> <td><code>tests/test_auth.py</code></td> <td>14</td> <td>JWT validation, RBAC, DB queries</td> </tr> <tr> <td><code>tests/test_payments.py</code></td> <td>24</td> <td>Payment CRUD, business logic, edge cases</td> </tr> <tr> <td><code>tests/test_db_schema_and_seed.py</code></td> <td>6</td> <td>Migration integrity, seed validation</td> </tr> <tr> <td><code>tests/test_logging_middleware.py</code></td> <td>7</td> <td>HTTP access logging, request/response capture</td> </tr> </tbody> </table> <h2 id="red-green-refactor"> <a class="anchor" href="#red-green-refactor" data-anchor="red-green-refactor" aria-hidden="true">#</a> Red-Green-Refactor </h2> <p>The authentication feature (<a href="https://linear.app/ppl-sira/issue/SIRA-26">SIRA-26</a>) followed strict TDD commit discipline. Each backend function got its own RED commit (failing test) followed by a GREEN commit (passing implementation) before any cleanup.</p>