6 ways AI can quietly sabotage your SDLC
AI makes coding cheap, but it doesn’t replace engineering judgment. Here are six ways AI agents can quietly undermine your SDLC, and what you can do about them.

AI makes coding cheap, but it doesn’t replace engineering judgment. Here are six ways AI agents can quietly undermine your SDLC, and what you can do about them.

We ran a council of AI reviewers on a real Strapi PR that shipped two bugs. It caught both, every time. Here’s how to build your own, and when it’s worth the extra tokens.

When software engineering emerged in the mid-20th century, shaped by pioneers such as Alan Turing, John von Neumann, Grace Hopper, Edsger Dijkstra, and later Fred Brooks, software was largely about logic, mathematics, and precise instructions for a machine. Programs were smaller, the gap between the implementation and the knowledge required to understand was relatively short, and much of the truth about a system could be found directly in its source code. The code was the documentation.

Not so long ago, I wrote an article about OWASP ASVS 5.0 (a comprehensive security checklist aiming for web applications). I mentioned there that AI security was intentionally left outside of its scope. There is now a brand new OWASP document specifically for filling this gap: AISVS. I've looked at this standard. Is it actually helpful when building an AI-enabled system?

Around 66,000 CVEs are expected in 2026. Most won't affect your code, but which ones will? A practical look at layered, AI-supported vulnerability triage.

For a bank, introducing autonomous coding agents is an architecture, security and governance problem. Here is how Visdom addresses data residency, machine-enforced boundaries, credential security, AI tracing, audit integrity, human oversight, code quality, test verification, organizational context and cost governance.

Most of the AI-generated code already in your codebase arrived through unsanctioned tools on personal accounts. This is Shadow AI — and like shadow banking before 2008, the risk is invisible until it isn't. Here's how to govern it with risk-based triage, traceability, and Continuous Modernization.

AI tools work. Adoption is above 80%. And yet measurable business value remains stubbornly low. The bottleneck is not the model — it's the software delivery system around it.

A coding agent is not an AI-native SDLC. Visdom provides the control plane — context, orchestration, sandboxing, and auditability — required to turn AI-generated code into software enterprises can trust in production.

Learn how to build a natural language search feature using AI and Amazon Bedrock. Translate user intent into secure, structured SQL or GraphQL queries without training custom LLMs.

Evaluating agentic systems is a multi-dimensional challenge that requires a multi-layered framework. A robust evaluation system must verify both functional and non-functional requirements. The system should verify whether an agent is fulfilling its core objectives, while performing efficiently, safely and with low latency. Furthermore, the system must account for scalability while ensuring the agent's underlying reasoning remains transparent and traceable. Those different evaluation layers allow, to evaluate the model both from the technical and strategic business perspectives.

A monthly reading roundup - no chasing every model, no top-50 lists, no marketing. One thread running through it all: the best model on the planet can be switched off on a Friday afternoon, so the real asset is what you build around it. You lease the model, but the process is yours.
