J'ai un aveu à faire : pendant longtemps, quand un dev me montrait fièrement son app Python avec un bouton gris carré et une Listbox qui sentait Windows 95, je hochais la tête poliment. Aujourd'hui, j'ai arrêté. Pas parce que je suis devenu méchant. Parce que PyQt6 existe, et qu'il n'y a plus aucune excuse. Cet article, c'est ma tentative de te convaincre — toi qui ouvres encore tkinter par réflex
AI Can't Fix What It Can't See: How cdk diagnose Enables Autonomous CDK Remediation Current Behavior vs. What We Want Today, when a CDK deployment fails through a pipeline, the remediation loop looks like this: Developer ──▶ Push code ──▶ Pipeline ──▶ CFN deploy ──▶ ❌ Fails │ ┌───────────────────────────────────────────────
You ask Claude to "add caching to the user profile endpoint," and 30 seconds later you ship something that looks fine in review: SET user_42 <json> — flat key, no namespace, collides the moment a second service shares the cluster. No TTL — the entry lives forever until maxmemory evicts your hottest keys. KEYS user_* in a cleanup job — single-threaded Redis stalls every other client for hundreds of
In my last article, I mentioned that my SAST tool uses regex-based pattern matching instead of AST parsing, and that this was a deliberate tradeoff. A few people asked me to go deeper on that decision — because on the surface, it sounds like I took a shortcut. I didn't. Or rather — I did, but it was an informed shortcut, and there's a meaningful difference. Let me explain what AST parsing actually
Why Most Crypto Bots Get Sandwiched (And How to Prevent It) If you've ever run a trading bot on Ethereum or Solana, you've probably experienced the frustration of watching your profitable trade get "sandwiched" - where some MEV bot frontruns your transaction and backruns it, stealing most of your profit. In this post, I'll explain exactly how these sandwich attacks work, why most bots are vulner
Engineering Craftsmanship: Building a Sovereign Immutable List in Java In an era of "vibe coding" and AI-driven bloat, there is a distinct value in returning to the fundamentals of structural integrity. As I navigate a career pivot toward Site Reliability Engineering (SRE) and Senior Development, I’ve found that the most resilient systems are those built on the principles of data sovereignty and
LLMs hallucinate. That's not news. What's underdiscussed is how that failure mode behaves in long working sessions: confident reconstruction that looks fluent, cites specifics, and feels right — until three sessions later when something supposed to be true turns out not to be. This is week 5 of an 8-week deep dive on CRAFT for Cowork, a structured working environment for Claude. The QA framework t
You don’t notice the problem right away. Everything runs smoothly in MySQL… until a new report shows up. Then queries slow down, dashboards lag, and you start realizing you’re stretching the database beyond what it’s good at. That’s usually when BigQuery enters the picture. So the real question becomes: How do you actually move data between them without turning it into a side project? Let’s w