Python on ppl-blog

Git, Linear, Discord: The Automation Layer That Replaced Manual Status Updates

Mon, 25 May 2026 00:00:00 +0000

The friction in team development isn’t usually the code. It’s the overhead around the code: knowing what’s in review, who’s working on what, whether a ticket moved, whether that MR you were waiting on is finally merged. Most teams solve this by adding a status-update ritual — a daily standup field, a manual Discord message, a ticket that someone remembers to update after they’re done. This works until someone forgets, or the meeting cadence doesn’t match the merge cadence, or you’re on a different timezone.

Static Analysis Isn't Optional: How We Built a Three-Tier Quality Gate for SIRA

Mon, 25 May 2026 00:00:00 +0000

There’s a version of static analysis that doesn’t work: you add a linter to CI, it flags style issues nobody fixes, the team learns to ignore the yellow warnings, and the tool becomes decoration. The failures it was supposed to catch go to production anyway.

The version that works is where the tool is in the critical path. It blocks the commit, or blocks the merge, or blocks the deploy. When it fires, something stops until someone fixes it. The tool has teeth.

TDD Isn't Enough: How Benchmarks Turned Green Tests Into Real Evidence

Fri, 22 May 2026 00:00:00 +0000

There’s a moment in TDD that every developer has hit: all the tests are green, coverage is at 90-something percent, and you’re still not confident the code is actually correct. Either the tests are testing the wrong things, or they’re testing the right things but missing a whole class of bugs that coverage metrics can’t see.

I hit that moment twice on the same feature while building SIRA, a FastAPI-based invoice reminder system. What pulled me out of it wasn’t more tests — it was a different kind of test.

Three SOLID Principles, One Design Decision: OCP, ISP, and LSP in a Real FastAPI Service

Thu, 21 May 2026 00:00:00 +0000

Most SOLID explainers cover all five principles in one pass, give you a definition and a toy example for each, and move on. What they skip is showing up in a codebase that already works, finding where a principle is being violated, and making the case that fixing it actually changed anything.

This post focuses on three: OCP, ISP, and LSP. They came up together in a single design decision on a FastAPI invoice-reminder service — and the interesting thing is that one construct in Python’s type system addresses all three at once.

Two Design Patterns I Applied in One MR

Thu, 21 May 2026 00:00:00 +0000

There’s a specific kind of file you learn to dread. Not broken — tests pass, CI is green, customers are using it. But you avoid it anyway. You touch it only when you have to, and when you do, you spend the first few minutes re-orienting: which method calls what, what side effects lurk where, whether there’s another spot you’ll forget to update.

ClientService was that file. 354 lines, tested, shipping. But every time I touched anything PII-related, I’d Ctrl+F the file to find every spot that called encrypt(), because I didn’t trust myself to remember all three. That reflex is the smell. I’d been ignoring it for weeks.