AI code review tools like CodeRabbit and Greptile are useful. But if the plan is to let the agent build it and then let the reviewer clean it up afterwards, you may already be too late. By the time a review tool sees the PR, the agent has already made the decisions that matter. It has chosen the shape of the implementation, made assump...

The people getting the most out of AI agents are not the best prompters. They are the best operators. Keep the human at the start of the loop and at the end of it. Let the agent own the middle. That is the whole job. Prompting is where everyone starts. Ask a sharper question, add more context, tweak the wording, try again. It works, an...

The fix for AI code review isn't more reviewers. It's making the code worth reviewing before it ever reaches one. Addy Osmani (Director of Cloud AI at Google) just wrote a sharp piece on this, and the numbers in it are brutal. Review duration up 441%. Zero-review merges up 31%. Defect rates climbing from 9% to 54% (Faros AI). Roughly 4...

Spec-first AI development is quietly rebuilding the one thing engineers spent a decade escaping: waterfall. The agent doing the typing won't save you from it — if anything, it makes the trap worse. That's why I'm sceptical of approaches like Spec Kit becoming the default way teams work with coding agents. Not because specs are bad. Spe...

Your next customer might not be human. On parts of the internet automated traffic already outnumbers people, yet most businesses still build their entire online buying experience for someone who is. Cloudflare has reported that automated traffic now overtakes human requests in parts of the internet. HUMAN Security found AI-driven traff...

AI can write more pull requests than your team can confidently review. Governed PRs are how you keep both — the quality bar and agentic speed. More PRs only help if review confidence keeps up. Otherwise every reviewer starts from scratch, asking the same questions before they can trust a single line. Did the agent follow our standards?...

AI code review asks whether the code looks okay. Governed delivery asks whether the change is acceptable. That distinction matters more every week, as more teams move to AI-assisted and agentic development. AI review tools are genuinely useful. They spot issues, suggest improvements, catch the obvious mistakes, and take some repetitive...

A year ago the message to engineers using AI was: use the agents fully, lean in, let them run. The ones burning the most tokens were read as the ones embracing the future — and rewarded for it. The cautious ones, the engineers asking what all this was costing, got quietly filed under not forward-thinking enough. Now the message is flip...

AI's immediate value is not automation. It is amplification. Most businesses have not figured that out yet, and it is costing them. They are asking "how do we automate this completely?" That question will matter eventually. In some areas it already does. But right now, for most real businesses — software delivery, operations, finance, ...

Too often it means more process, more forms, more meetings, more gates, and more delay. Red tape dressed up as control. That is not what I’m trying to build with Software Dark Factory. The point of SDF is not ceremony. It is to help teams keep useful delivery moving while making AI-assisted work easier to review, trace, and challenge. ...

Old delivery had a slow feedback loop. Friction built up over months. Slow test suites, review bottlenecks, unclear ownership, repeated governance steps. Someone eventually noticed and maybe it got fixed. With AI-assisted delivery, that loop is too slow. The system moves faster, which means waste compounds faster. And the cost isn't ju...

AI-assisted software delivery changes how teams measure the cost of engineering work. That sounds like a finance sentence, but I do not think this is mainly a finance problem. It is a delivery problem. For a long time, the cost of a software change was mostly hidden inside human effort. How long did it take to understand the request? H...

That is the thought that kept coming back as I tried to work out what AI coding agents should change about software delivery. The pressure right now is real: move faster, ship more, use the agents properly, let the tools take more of the work. I understand the pressure. I also understand the appeal. But a lot of what gets described as ...

More engineering teams are talking openly about agents auto-merging PRs. The reaction is predictable — half excitement, half horror. The excitement is understandable. If your AI agent can write the code, pass the tests, and merge the PR without anyone waiting in a queue, that is a genuinely faster delivery loop. The speed case is real....

Your team is shipping faster. Your review queue is longer. That’s not a coincidence. This is the pattern I keep seeing from engineering leaders, founders, and developers who have adopted AI-assisted development seriously: the output speed is real, but the delivery model hasn’t caught up. PR review backs up. Rework increases. Decisions ...

You have written this line. So have I. def can_access? stripe_subscription_id.present? endIt looked fine at the time. Probably week three of the project. Billing was working, Stripe was sending webhooks, and access was gating correctly. Ship it. That line is not a billing integration. It is a governance failure you have deferred. Here ...

Specs are useful. They are not governance. Spec Kit exists because vibe coding made an old software problem suddenly more dangerous. Vague intent has always produced bad software. The difference now is speed and plausibility. A loose prompt no longer produces only a rough prototype. It can produce a feature-shaped object with files, te...

Once I had the engineering side of the Dark Factory model working, governed pull requests, agentic workflows with clear handoffs, playbooks applied on every PR, a different problem became obvious. Engineering was touching marketing surfaces. And marketing had no equivalent governance layer. That is not a complaint about marketing. It i...

Governance is not something I learned from a book. It is something I could not afford to get wrong. Twenty years of working in startups does something to the way you think about shipping software. Not because startups are glamorous or fast or any of the things people say. But because in a small team, there is nobody to hand the respons...

Building the engineering side of the Dark Factory operating model was easier than I expected, and the reason was clear in retrospect: I had 20 years of SDLC experience to draw on. I already knew what a good pull request workflow looked like. I knew what a reasonable CI/CD pipeline should do, how code review should work, what a deployme...

AI learns the same way a junior engineer does. Through reinforcement. Through feedback. Through someone watching closely enough to catch the drift early and correct it before it becomes a habit. Most people do not think about it that way. They treat an agent like a search engine with ambition — give it a task, expect a result, get frus...

People talk about agentic workflows as if they need a completely different set of principles. I think the opposite. The more I work with coding agents, the less I think the winning teams will be the ones with the cleverest prompts or the strongest models. I think they will be the teams that understand software engineering discipline de...

A diff tells you what changed. A governed PR should tell you why it exists. That is why PR summaries in the factory now include a Why section near the top. This sounds like a small template change, but it fixes a real review problem. Without it, the reviewer has to reconstruct intent from implementation detail. They read the code, infe...

If a product is meant for technical people who already work in agent-native tools, setup should not begin by pulling them into another dashboard. That was one of the product decisions I cared about most with Explore. Too many tools still claim to fit modern technical workflows, but the first real step is the same old pattern: open a br...

A static CV can still introduce someone. It just does less proof work than it used to. It is easy to make a profile look polished now. Cleaner summary. Better phrasing. Tidier bullets. That part got cheap. If you want stronger signal, you need something people can actually inspect, with more depth, more context, and a better next quest...

AI made polished summaries cheap. That is useful for cleanup, but it is not useful for differentiation. A static CV can still do the first job. It can tell someone where you worked, what you shipped, what stack you used, and what kind of roles you have had. But it does not do much proof work anymore. If everyone can generate a cleaner ...

This is the part I care about most now. Agents writing code is no longer the interesting part. That part is already here. They can move fast, write code, fix bugs, add tests, work through a codebase, and get a surprising amount done without much friction. We know that now. What matters is whether any of that can be trusted enough to ca...

A few people have asked whether Explore only works with Codex. It doesn’t. It now works with Codex, Claude Code, OpenCode, and Cursor through the same shared flow. That matters because I have no interest in building the same integration four times and pretending that counts as product work. That game never ends. New tool, new wrapper, ...

My software dark factory behind Explore is an end-to-end agentic operating platform with governance built in. Development governance earns trust before merge. Production governance proves the intended outcome is actually live. The release lane bridges the two, and smoke testing turns confidence into evidence.

AI made polished summaries cheap. That is good for formatting. It is bad for proof. A strong engineer can now look polished in an afternoon. Clean headline. Sharp summary. Sensible project bullets. Nice phrasing. None of that is hard anymore. The problem is that polish used to do more proof work than it does now. It suggested care. It ...