Articles.

In ticket triage, the model's mistake is the wrong queue, and wrong queues can be counted

AI that picks vs AI that writes: where each belongs in your system

Closed decisions (classify, route, validate) call for a model that picks and errors you can count. Free text needs human review. How to decide and test it, with Jev as the case.

Sep 18

The first question is the simplest: what can you open on your phone when the sprint ends

App developers for hire: 5 questions to ask before you sign

Five questions a non-technical founder can ask app developers for hire to spot a failing project in month one, plus freelancer vs fixed-bid vs dedicated team.

Sep 18

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

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 fifth question is the one nobody answers without opening the repository

AI software development without architecture: 5 checks before month six

Building with AI without architecture breaks around month six. Five checks you can run without reading code, what each answer means, and the cheaper path before a rewrite.

Sep 4

6min read

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

The rule that decides commission usually lives in three places at once, with different values

Thousands of IF/THEN/ELSE rules: code, engine or spreadsheet

Rules that change weekly belong in versioned data with an owner. Rare rules stay as ifs. When a rules engine pays off, and what the finance spreadsheet really costs.

Aug 31

Before the first member goes up, the structure already has stamped drawings and a signature behind it

Why can't IT deliver big projects on time like construction?

Construction slips too. Three contract devices explain the gap: a paid design phase, signed change orders with measurement, and one named engineer of record.

Aug 28

The most expensive rule in the company usually lives in two places: this whiteboard and one person's head

Technical debt you cannot see: measuring cognitive debt

The most expensive technical debt is the rule only one person can explain. A 40 minute test to find that concentration, and what to do once it shows up.

Aug 26

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

No contractor prices a foundation before the soil test. In software, the drill is opening the piece nobody has looked at.

How to respond when you are asked for an estimate

Answer with a range, the part nobody has measured yet, and the date you tighten the number. Why the deadline question fails and what to measure first.

Aug 21