<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><title>hackers&amp;wizards Blog</title><link>https://www.hackersandwizards.dev/blog/</link><atom:link href="https://www.hackersandwizards.dev/blog/rss.xml" rel="self" type="application/rss+xml"/><description>Definitions, research and field notes on agentic engineering, each with its sources and limits.</description><language>en</language><lastBuildDate>Sun, 01 Nov 2026 00:00:00 GMT</lastBuildDate><sy:updatePeriod>daily</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>Measuring AI impact on engineering: what to count and what to ignore</title><link>https://www.hackersandwizards.dev/blog/2026/measuring-ai-impact/</link><guid>https://www.hackersandwizards.dev/blog/2026/measuring-ai-impact/</guid><pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate><description>Code volume, pull requests, usage: AI pushes up every number that is easy to count. A Stanford talk and DX data put the measured gain at around 10 percent, and it swings widely from company to company. What to measure instead, where the returns come from, and why things get worse before they get better.</description></item><item><title>Breaking the Loop: Why agents never finish on their own</title><link>https://www.hackersandwizards.dev/blog/2026/breaking-the-loop/</link><guid>https://www.hackersandwizards.dev/blog/2026/breaking-the-loop/</guid><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate><description>Agents in a software factory always find another problem, another ticket, another improvement. Only a second, much slower loop can say when the work is finished: the one that reaches the market.</description></item><item><title>A label on an issue is the whole protocol between agents</title><link>https://www.hackersandwizards.dev/blog/2026/development-workflow/</link><guid>https://www.hackersandwizards.dev/blog/2026/development-workflow/</guid><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><description>The development-workflow skill in the software-factory.dev factory is the factory's own map of itself. It shows that the automations never call each other: they coordinate through labels on issues.</description></item><item><title>Report the daily delta, not the total that only goes up</title><link>https://www.hackersandwizards.dev/blog/2026/tweet-drafter/</link><guid>https://www.hackersandwizards.dev/blog/2026/tweet-drafter/</guid><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><description>The Tweet Drafter in the software-factory.dev factory posts updates three times a day and reports the daily delta, not the cumulative total, because a total always looks like progress.</description></item><item><title>An automated status report is only as honest as its prompt</title><link>https://www.hackersandwizards.dev/blog/2026/weekly-recap/</link><guid>https://www.hackersandwizards.dev/blog/2026/weekly-recap/</guid><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><description>The weekly recap automation in the software-factory.dev factory stays honest because the honesty is written into its prompt: the challenges section is what makes it authentic, and an unrecorded number has to be named as unrecorded.</description></item><item><title>A metric without a red line is decoration</title><link>https://www.hackersandwizards.dev/blog/2026/performance-monitor/</link><guid>https://www.hackersandwizards.dev/blog/2026/performance-monitor/</guid><pubDate>Tue, 25 Aug 2026 00:00:00 GMT</pubDate><description>The weekly Performance Monitor in the software-factory.dev factory works because every metric it watches has a hard threshold written into it.</description></item><item><title>An automation that audits the factory must not rewrite its own record</title><link>https://www.hackersandwizards.dev/blog/2026/automation-auditor/</link><guid>https://www.hackersandwizards.dev/blog/2026/automation-auditor/</guid><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><description>The automation auditor in the software-factory.dev factory inspects every other automation on the line. Its most useful rule: it may never overwrite last week's audit.</description></item><item><title>Escalated work needs a return path back onto the line</title><link>https://www.hackersandwizards.dev/blog/2026/needs-human-requeue/</link><guid>https://www.hackersandwizards.dev/blog/2026/needs-human-requeue/</guid><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><description>The smallest automation in the software-factory.dev factory puts escalated issues back on the line once a human has answered. The return path from human to machine needs its own owner.</description></item><item><title>Set the stale-work clock from your agents' cycle time</title><link>https://www.hackersandwizards.dev/blog/2026/stale-issue-reviewer/</link><guid>https://www.hackersandwizards.dev/blog/2026/stale-issue-reviewer/</guid><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><description>The Stale-Issue Reviewer at software-factory.dev calls work stale after three hours, not three days, because a watcher's clock has to run at the speed of the line it watches.</description></item><item><title>The PR Shepherd resolves only the conflicts it understands</title><link>https://www.hackersandwizards.dev/blog/2026/pr-shepherd/</link><guid>https://www.hackersandwizards.dev/blog/2026/pr-shepherd/</guid><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><description>The PR Shepherd in the software-factory.dev factory rebases conflicted pull requests but hands semantic conflicts to a human. The hard part of automation is encoding where its competence ends.</description></item><item><title>Verify UI components in the page they ship in</title><link>https://www.hackersandwizards.dev/blog/2026/ui-verifier/</link><guid>https://www.hackersandwizards.dev/blog/2026/ui-verifier/</guid><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><description>The UI Verifier in the software-factory.dev factory screenshots every changed component twice, in isolation and in the real page, because a component that passes in isolation can still fail where it ships.</description></item><item><title>Coding agents are an organizational-design problem</title><link>https://www.hackersandwizards.dev/blog/2026/coding-agents-organizational-design/</link><guid>https://www.hackersandwizards.dev/blog/2026/coding-agents-organizational-design/</guid><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><description>Cheaper local generation pushes the coding-agent constraint into team practice, the shared platform, governance, and learning. One practitioner's four-level model of that shift, held up against what DORA can and cannot support.</description></item><item><title>Why faster coding does not guarantee faster delivery</title><link>https://www.hackersandwizards.dev/blog/2026/coding-speed-delivery/</link><guid>https://www.hackersandwizards.dev/blog/2026/coding-speed-delivery/</guid><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><description>Productivity research measures task time, perceived savings, pull requests, and production flow, each in its own way. Read side by side, the measures show where the constraint moves.</description></item><item><title>Software Factory evidence and its limits</title><link>https://www.hackersandwizards.dev/blog/2026/factory-evidence/</link><guid>https://www.hackersandwizards.dev/blog/2026/factory-evidence/</guid><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><description>Public implementations show that agent-run delivery systems can build and ship software. Read their numbers with a source label, a scope, and careful limits.</description></item><item><title>Verification in a Software Factory</title><link>https://www.hackersandwizards.dev/blog/2026/factory-verification/</link><guid>https://www.hackersandwizards.dev/blog/2026/factory-verification/</guid><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><description>When generating code gets cheap, a Factory's throughput depends on how well the system can establish that a change is acceptable, safe, and worth shipping.</description></item><item><title>Green CI does not prove the live site works</title><link>https://www.hackersandwizards.dev/blog/2026/post-merge-verifier/</link><guid>https://www.hackersandwizards.dev/blog/2026/post-merge-verifier/</guid><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><description>The Post-Merge Verifier in the software-factory.dev factory smoke-tests the real production site after every merge, because passing tests and a working site are two different claims.</description></item><item><title>What is a Software Factory?</title><link>https://www.hackersandwizards.dev/blog/2026/what-is-software-factory/</link><guid>https://www.hackersandwizards.dev/blog/2026/what-is-software-factory/</guid><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><description>A Software Factory coordinates agents, context, deterministic gates, and human decisions across the path from intent to production.</description></item><item><title>An auto-merging PR reviewer is safe once it knows when to stop</title><link>https://www.hackersandwizards.dev/blog/2026/pr-reviewer/</link><guid>https://www.hackersandwizards.dev/blog/2026/pr-reviewer/</guid><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><description>The PR Reviewer in the software-factory.dev factory merges code with no human approval. One number makes that safe: it gives up after three failed attempts to fix CI.</description></item><item><title>Daily metrics that cannot drift: subtract yesterday's total</title><link>https://www.hackersandwizards.dev/blog/2026/daily-metrics/</link><guid>https://www.hackersandwizards.dev/blog/2026/daily-metrics/</guid><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate><description>The Daily Metrics automation in the software-factory.dev factory never measures a daily change with a date-filtered query. It subtracts yesterday's cumulative total from today's, a method that cannot drift.</description></item><item><title>A bug-fix automation must never exit quietly</title><link>https://www.hackersandwizards.dev/blog/2026/bug-fixer/</link><guid>https://www.hackersandwizards.dev/blog/2026/bug-fixer/</guid><pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate><description>The bug-fix automation in the software-factory.dev factory has two ways to end a run: it ships a fix or escalates to a human. Honest failure is a feature you have to design.</description></item><item><title>The Feature Builder checks for open bugs before it builds</title><link>https://www.hackersandwizards.dev/blog/2026/feature-builder/</link><guid>https://www.hackersandwizards.dev/blog/2026/feature-builder/</guid><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate><description>The software-factory.dev build automation runs a pre-flight check first: a priority-1 or priority-2 bug nobody has picked up stops all new feature work.</description></item><item><title>An improvement automation needs a cap on its ambition</title><link>https://www.hackersandwizards.dev/blog/2026/product-improver/</link><guid>https://www.hackersandwizards.dev/blog/2026/product-improver/</guid><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><description>The Product Improver in the software-factory.dev factory files at most three issues a run, and zero when it finds nothing worthwhile.</description></item><item><title>Fix the incident and the rule in the same commit</title><link>https://www.hackersandwizards.dev/blog/2026/incident-responder/</link><guid>https://www.hackersandwizards.dev/blog/2026/incident-responder/</guid><pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate><description>The Incident Responder in the software-factory.dev factory updates the conventions document in the same commit as the fix, so the rule that would have prevented the bug is there before the next change.</description></item><item><title>Cross user feedback against usage before it becomes work</title><link>https://www.hackersandwizards.dev/blog/2026/feedback-digest/</link><guid>https://www.hackersandwizards.dev/blog/2026/feedback-digest/</guid><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><description>The Feedback Digest in the software-factory.dev factory reads new feedback next to seven days of usage data, and files an issue only when the evidence backs it.</description></item><item><title>The Feature Planner writes its own backlog, behind a human gate</title><link>https://www.hackersandwizards.dev/blog/2026/feature-planner/</link><guid>https://www.hackersandwizards.dev/blog/2026/feature-planner/</guid><pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate><description>The triage automation in the software-factory.dev factory also writes its own backlog when the line runs dry, and routes anything risky through a person first.</description></item></channel></rss>