Tech news from the best sources
The ask was simple: the PR was 3,000 lines and nobody wanted to review it. The agent split it into three PRs — one for the write path, one for the a…
Most extractions do not fail in review. They fail two weeks later, when a test hits a module global nobody remembered. The repair costs more than th…
The smallest safe change is a measurable claim. Most refactors fail because nobody defined "small." A rename here. A default flipped there. Six week…
Characterize the Boundary, Not the Module: An Import-Graph Gate for Messy Refactors The rule: characterize only the symbols other modules import. Th…
The function looked wrong. It returned an object with a key that started with a dollar sign, it did a network call inside a loop, and it mapped one…
The PR diff looks fine. You asked the agent to add a phone-number validator. It added a file called validation-helpers.ts with a clean, well-tested…
Conclusion first: in a messy repo, the refactor usually breaks files, not stdout. Teams write golden tests for console output. Almost nobody asserts…
The refactor PR looks clean. getUserById becomes fetchUserById , the body moves to a new service file, and the tests pass. At the bottom of the diff…
A messy freshness check should not be rewritten in one pass. Freeze the observed outputs before any cleanup begins. Then move one comparison inside…
The rename that looks safe You ask the agent to rename process_payment to settle_payment . It runs across the codebase, updates every import, rename…
The diff that looks like a win You hand the agent a 40-line helper that's been in production since 2022. You ask it to "clean this up." Thirty secon…
Freeze Aging Labels Before One Status Extract Pin current aging labels before you trust a cleanup diff. Extract one status rule only after those lab…
Pin apply order before you extract one discount rule. A free coding pass can draft the smallest patch. Frozen checks still decide whether that patch…
A scored cut beats a wide cleanup every time. Pick the change with the lowest caller risk. Golden tests then guard that one extract, and nothing els…
The big bang rewrite is the most confident decision an engineering team can make and one of the worst. The pitch is always reasonable. The current s…
Every tuning change needed a code review, a release, and a week of store rollout. So we stopped tuning, which is the worst possible outcome. Eightee…
Extract one mutator only after tests pin object identity. Value equality alone hides alias bugs in shared containers. A copied list can match every…
A Psychological State is a Coefficient Vector Richard Emate Richard Emate Richard Emate Follow Sep 23 A Psychological State is a Coefficient Vector…
There is a lot of literature about how to refactor code and what techniques to apply, but sometimes we forget one important aspect: the human factor…
Pin the query-string contract before any helper extract. Extract one encoder only after those bytes stay frozen. Messy HTTP clients scatter urlencod…
Characterization Tests First, Then the Smallest Safe Change Stop refactoring. Start recording. The smallest safe change wins only if you can prove n…
Every mainframe migration begins with someone searching for mainframe migration tools, and every vendor demonstration that follows looks remarkably…
A detector in my build looks for repeated code shapes. It caught a ten-line window shared between two checks that I had written deliberately, days a…
Mainframe modernisation is rarely a single decision. It is a choice between several distinct strategies, each with a very different cost, timeline,…
A messy repo does not need a rewrite first. It needs a frozen output tree as the oracle. Then you extract one pure helper. Stop there. AI diffs look…
COBOL still underpins a vast amount of the software running in UK banks, insurers, public sector bodies, and large retailers. Much of it processes m…
Most messy-repo risk lives in silent caller contracts. Capture current observable outputs before any helper edit. Then apply the smallest safe behav…
The biggest refactor failures come from big steps. A 200-line function turns into a rewrite. The rewrite ships with a regression. The fix is to make…
Refactoring at enterprise scale is a different discipline from refactoring in an IDE. Renaming a method across one service is a right-click; retirin…
Most refactors die quietly while the test suite stays green. The bug ships because the change was too wide. A safe refactor touches one branch at a…