Black October: What the First AI-Agent Attack Wave Means for Every Business
Black October saw AI agents breach 100+ companies on a $5,000 token budget. What the first AI-agent attack wave means for patch speed and defenses.
We've written about how AI is changing software development in general. This post is more specific: how we actually work with AI day to day, what we refuse to automate, and what that means if you hire us. Transparency here matters — if you're evaluating a development partner, "do you use AI?" should get a straighter answer than a shrug or a sales pitch.
AI-assisted coding, human-owned code. Our developers use AI coding assistants throughout implementation — scaffolding features, writing routine logic, exploring unfamiliar APIs, drafting migrations. But every line that reaches a client codebase goes through the same gate it always has: a human developer reviews, tests, and takes responsibility for the change. Nothing merges because "the AI said so." In practice, AI writes a first draft; our engineers decide what survives.
AI-assisted testing. We use AI to generate unit tests and surface edge cases we might not have listed by hand — empty inputs, timezone quirks, concurrent updates. This has genuinely improved coverage on our projects, because test-writing time used to be the first thing squeezed by deadlines. The tests themselves get reviewed like any other code; a wrong test that passes is worse than no test.
Drafting documentation. AI drafts API docs, setup guides, and handover documentation from the code, and a developer who knows the system corrects and completes them. The result is that our projects ship with better documentation than the industry norm — not because AI writes great docs, but because it removes the blank-page excuse for not writing them at all.
Code review support. Before a human reviews a pull request, an automated pass flags obvious issues — missed error handling, inconsistencies, potential bugs. Human reviewers then spend their attention on the things machines are bad at: whether the change fits the architecture, whether it's solving the right problem.
Just as important is where we deliberately keep humans in charge:
We're also careful about data. Client code and business information only go through AI tools whose terms we've vetted, and when a client has stricter requirements — regulated industries, sensitive IP — we adapt our tooling to match, and we're happy to put that in writing.
The honest version of the benefit, without inflated multipliers:
We've applied this workflow across client projects and our own products — Rukrok, Komerce, and Chargly — which gives us a useful feedback loop: we feel the consequences of our own practices in systems we maintain ourselves.
AI-assisted development is not magic, and we'd rather under-promise:
If you're comparing vendors, we'd encourage you to ask every candidate the questions in our guide to choosing a development company — including exactly how AI-generated code gets reviewed before it ships. Any team using these tools seriously will have a specific answer.
Want to see how this workflow would apply to your project — or just want straight answers about AI-assisted development before you commit to anyone? Get in touch. We'll walk you through our process and where it does (and doesn't) help your case.
Black October saw AI agents breach 100+ companies on a $5,000 token budget. What the first AI-agent attack wave means for patch speed and defenses.
What software maintenance costs per year, covering the 15–25% of build cost rule, the corrective, adaptive, and perfective split, and how to budget it.
SaaS development cost in 2026 broken down by stage, from MVP through growth to enterprise budgets, what each stage includes, and the costs after launch.