Part 2 of 5 in The New Engineering Contract - what it means to lead engineers when AI is doing more of the coding. Stripe never skipped the boring stuff. They ship 1,300 AI PRs a week. Amazon skipped it. Their storefront went down for six hours. Kent Beck wrote the answer in Extreme Programming Explained in 1999. We read it. Then chose velocity anyway. A friend of mine leads engineering at a funde
A month ago, we launched Veltrix. No brand recognition. No paid ads. No outbound spam. Just a small team with one clear focus: build infrastructure that actually works when it matters. In the first 30 days, we closed 3 major deals in Georgia. That wasn’t part of the plan. We expected a slow start — maybe a few small clients, some testing, iteration. Instead, we immediately saw something intere
Comments
Diving into blockchain data (Solana specifically) changed how I think about “data” entirely 👇 At first, I expected something like a clean database—tables, rows, easy queries. ⚡ The “click” moment: 🧩 Biggest surprise: 🆚 Compared to traditional APIs: 🚧 Still learning: It’s less “database access” and more “state archaeology.” And that shift changes everything.
I've been frustrated with querySelectorAll performance in high-frequency scenarios for a while. On large DOMs (10k+ nodes) with 50–100 queries/second — think virtual DOM diffing, live dashboards, design tools — it becomes a real bottleneck. So I built AQE (Atomic Quantum Engine): a CSS selector engine that replaces tree traversal with flat, memory-mapped bitwise operations. HOW IT WORKS Every DOM
If you've ever used a bottleneck calculator, you've probably seen a simple percentage telling you whether your CPU or GPU is holding your system back. But here’s the truth most people don’t realize: Bottlenecks are not fixed numbers — they are dynamic, workload-dependent behaviors. In this post, we’ll go beyond basic tools and break down how CPU and GPU bottlenecks actually work in real-world scen
Ages ago when CSS grids came with a repeat() function to simplify defining repetitive columns and rows, I was not alone in wishing for this function to be made generic and work in any context. After seeing Wes Bos on BlueSky wishing for this exact concept, specifically for repeating segments in a shape() definition, I chimed in with my +1's on making repeat() generic across CSS Without delay, @no
Every AI coding agent ships with the same problem: it knows syntax but not discipline. It can write a React component or debug a segfault, but it won't ask "did I verify this actually works?" before declaring victory. It won't split a 400-line diff into reviewable chunks. It won't check if the fix it's about to apply matches the root cause it claims to have found. I've spent the past six months fi