Articles.

The upgrade ticket that never makes the sprint is the one that turns into a frozen quarter

Incremental migration vs big-bang: what each one costs your roadmap

Upgrades of the same tech belong in every sprint. A different tech is a project, and even that ships in slices. What each path costs and where the rule breaks.

Sep 15

8min read

The cores are busy around the clock. The question is who is on the other end.

Scraper traffic is inflating your cloud bill: how to measure it

At git.kernel.org, 14 CPU cores do nothing but render pages for scrapers, more than all legitimate access combined. How to split bots from humans in your logs first.

Sep 9

The platform everyone called obsolete can still tell you what it did yesterday

Mainframe and AI: legacy modernization is about missing logs and owners, not age

CIO Dive reports AI agents helped sustain confidence in the mainframe. Three checks that tell you whether your system is legacy, and what to do about each one.

Sep 2

Old code is usually the only living documentation of the rules your revenue depends on

Legacy modernization: upgrade PHP 5.6 to PHP 8 or full rewrite?

Upgrading PHP 5.6 to PHP 8 usually costs less than a rewrite. Three measurements (compatibility, dead dependencies, revenue flows without tests) tell you if your case is the

Aug 24

8min read

PR volume went up and the review queue is where the AI gain disappears.

AI software development: teams ship more code and deliver less. What to measure

PR volume is up and the product hasn't moved. Four measurements that expose where AI turns into debt: review queue, 30-day rework, mutation score and real customer use.

Aug 19

Inheriting an undocumented system starts with understanding what already runs in production

Legacy system modernization: the first two weeks with 200K lines of spaghetti code

The first two weeks on an undocumented legacy codebase: boot it from scratch, instrument production, map the five revenue paths. And why the day-4 rewrite call backfires.

Aug 14

A screen full of passing test files never tells you, on its own, whether any of them actually checks a result.

High test coverage is where production bugs hide best

A founder sent me a 92% coverage badge the same night his checkout was down. Coverage counts lines that ran, not results anyone checked, and it is the easiest number for a vendor to inflate. What a senior squad reads before it trusts the green.

Aug 7

5min read

A desk in the dark, lit only by a monitor with code open and a sticky note that reads "DO IT": the product keeps running while no one is watching.

Who Found the Outage First — You or Your Customer?

The vendor dashboard was green while checkout was down. The problem is not that systems fail, it is the order people find out: the customer before the vendor you pay to watch it. On why real monitoring measures symptoms, not CPU.

Jul 31

6min read

A complete team, managed by the vendor: the model behind the buzzword

Staff augmentation services: what a dedicated development team is and when it makes sense

Squad as a service means a complete engineering team on a flat monthly fee: defined seniority, technical leadership, and delivery managed by the vendor. In this guide: what the model really is, what gets disguised under the name, what it costs in 2026, and how to decide if it fits your stage.

Jul 23

6min read

Frost taking over a branch: the freeze starts slow, and almost nobody notices.

The stack you never update sends its bill without warning

I keep reviewing products running on versions that died years ago, and the pattern holds: nobody decides to freeze the stack, it freezes on its own because maintenance never fits into any budget. The bill shows up all at once on a bad day, and the teams that tend to it weekly almost never let it show up.

Jul 17

6min read

The product is yours on paper. The key sometimes lives on another company's keyring.

Who owns the code in software outsourcing? The answer is usually worse than you think

I watched a healthtech spend 23 days getting admin access to its own repository. On paper the code was theirs. In practice it was not. On the gap between owning something in a contract and owning it for real, and the half-hour test that shows which side you are on.

Jul 3

5min read