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 ...

Today I had the marketing agents review one of Explore’s public pages against the brand, mission, and source-of-truth docs we’ve set for the product. They identified a few bounded improvements, packaged them into a clean handoff, and passed the approved changes to engineering. Engineering then picked up that brief, made the scoped page...

A lot of companies seem to think agent accessible means they added a chatbot. It doesn’t. A chatbot is just a new way to talk to the old interface. An agent-accessible app is something an agent can actually use. That means it can understand what the product does, what actions are available, what state it is in, what constraints apply, ...

I’ve been thinking about mobile for Explore. Not because every product needs an app. And not because “launched a mobile app” looks nice on a CV. The more interesting question is: what would mobile teach me about the product, and what would it teach me about the factory? Explore is a Rails product. My dark factory is also primarily Rail...

The interesting part is not the CLI. It’s the login flow. Run explore login, approve it in the browser, and your agent gets authenticated access to the real app. Not a toy sandbox. Not a pasted API key. Not some half-baked “AI feature”. The actual app. This is where software is going. We’re moving from “has an API” to “an agent can act...

I’ve been testing that with Explore. Using the Explore CLI, I gave Codex my latest CV and asked it to compare it to my current Explore profile, recommend the right updates, and apply the relevant changes without touching my writing. Within a few minutes, the profile was updated and live. That is the interesting bit for me. Not just a n...

Explore started as a better proof surface for humans. That was the original idea. Something better than a static CV or polished personal site. Something that let people go deeper into the real signal behind a person’s work, writing, projects, and judgement. But it became clear to me that profiles no longer only need to be readable by h...

I’ve been increasingly concerned by the level of anxiety across our profession. I keep seeing very good engineers, people with real experience, strong judgement, and excellent CVs, feeling uncertain about how to stand out in a market that suddenly feels much more crowded and much noisier than before. A lot of that gets framed as “AI wi...

At that point, it stops feeling like an AI coding assistant and starts feeling like an operating model. The factory is now taking on more responsibility across the path from spec to shipped: auto-merge, production deploy, and verification. I’ve started scoring it against StrongDM’s software factory maturity classification, and on my cu...

A lot of operational pain gets misdiagnosed as a tooling problem or a headcount problem. At small scale, experienced people can often bridge the gaps. They remember the exceptions, know which signals matter, spot what needs doing next, and carry a lot of context in their heads. That works for a while. But as volume, variation, and oper...