From autocomplete to agents

The first wave of AI coding tools completed lines and functions. The current wave plans and executes multi-step tasks — reading a codebase, writing code across several files, running tests, and iterating on failures with limited supervision. That’s a change in kind, not just speed: the unit of work an AI touches has grown from a line to a feature, and the human’s job has shifted from typing to reviewing and directing.

Standardized plumbing is enabling standardized agents

Protocols like MCP are doing for AI tool access what REST and later GraphQL did for web APIs: turning bespoke integration work into a shared, reusable layer. That standardization is what makes it economical to build agents that reach into real systems, rather than agents that only talk. See our companion piece on what MCP actually is.

The bottleneck has moved, not disappeared

Code generation was rarely the actual constraint on software delivery — requirements clarity, architectural judgment, and review capacity were. AI tooling makes the easy 80% of implementation faster, which means the remaining 20% — the ambiguous requirements, the cross-system trade-offs, the “is this actually the right thing to build” conversations — is now a larger share of where a team’s time goes.

What we’d actually bet on

• Brownfield-aware AI coding practices becoming table stakes, not a specialty (see our piece on brownfield vs. greenfield).
• Agentic workflows handling more internal, reversible work before they’re trusted with customer-facing actions.
• Governance — audit trails, approval gates, rollback paths — becoming a normal line item in AI project scope.
• Model and provider choice being treated as a swappable architectural decision rather than a permanent commitment.

Summary: None of this requires believing AI will write all the code or none of it. It requires paying attention to where the actual mechanism has changed, and building the engineering discipline around it before the incidents force the issue.

#AI #SoftwareDevelopment #AgenticAI #FutureOfWork #SazkoSolutions

Published by Sazko Solutions – Driving Innovation in AI-Powered Software Delivery

The post The Future of AI in Software Development: What’s Actually Changing appeared first on Sazko Solutions.

What formal verification actually gives you

Ordinary testing checks the cases you thought of. Formal verification proves a property holds for all possible inputs — no counterexample exists. The catch has always been cost: writing those proofs by hand is slow, specialised work, so it’s reserved for avionics, cryptography, and a handful of other domains where failure is catastrophic.

Why AI assistance changes the economics

If a model can draft a proof that a human then checks and refines, the cost of verifying a critical component drops. That potentially widens the set of software worth verifying — payment logic, access control, safety interlocks — beyond the domains that can currently afford it.

The realistic near-term picture

• Verification stays expensive and specialised, just less so.
• The model drafts; humans still own correctness and the specification itself.
• The hardest part remains writing a specification that actually captures what “correct” means — AI doesn’t remove that.

Summary: AI-assisted formal verification won’t make every system provably correct. It might make it affordable to prove the handful of components where a bug is unacceptable.

#AI #FormalVerification #SoftwareEngineering #CriticalSystems #SazkoSolutions

Published by Sazko Solutions – Driving Innovation in High-Assurance Software

The post Formal Verification Meets AI: Why Machine-Checked Proofs Matter for Critical Systems appeared first on Sazko Solutions.

One-shot vs. long-running

A one-shot agent takes a request and returns a result; if it’s wrong, you try again. A long-running agent holds a goal across hours or days, accumulates state, and takes many actions before anyone checks the outcome. The failure modes are different: drift, compounding small errors, and actions taken on stale assumptions.

What “learning between sessions” needs from you

• A durable record of what the agent did and why, that both the agent and a human can review.
• Checkpoints where a person confirms direction before the agent commits to the next phase.
• Clear boundaries on what the agent can change without approval, especially as it gets more autonomous.

The trust curve

Agents that improve over time are more useful and harder to reason about — the thing making decisions this week isn’t quite the thing you evaluated last month. Treat capability growth as a reason to strengthen oversight, not relax it.

Summary: Long-running, self-improving agents are a real step forward in usefulness. The operational discipline they require is a step up too, and it doesn’t come in the box.

#AI #AgenticAI #Automation #EnterpriseAI #SazkoSolutions

Published by Sazko Solutions – Driving Innovation in Agentic AI and Automation

The post Agents That Learn Between Sessions: The Move to Long-Running AI Workflows appeared first on Sazko Solutions.

Why defence is a natural fit

Finding bugs is pattern-matching at scale across enormous codebases — exactly the kind of tedious, high-volume analysis that models are good at and humans burn out on. An AI system can read every file, flag suspicious patterns, and draft an explanation of why something might be exploitable, leaving humans to judge severity and fix.

The double-edged part

The same capability helps attackers. The realistic expectation for the next few years is a faster loop on both sides — quicker discovery, quicker patching, and less time between a vulnerability becoming known and becoming exploited. Organisations that patch slowly are more exposed in that world, not less.

What to actually do

• Assume vulnerability discovery is accelerating and shorten your patch cycles accordingly.
• Use AI-assisted scanning on your own code before someone else’s tool finds the problem.
• Keep a human in the loop for triage — false positives at volume waste more time than they save.

Summary: AI-assisted security is not a product you buy once; it’s a faster clock everyone is now running on. The teams that stay safe are the ones that speed up their response to match.

#AI #Cybersecurity #AppSec #DevSecOps #SazkoSolutions

Published by Sazko Solutions – Driving Innovation in Secure Software Delivery

The post AI for Defensive Security: What the Industry’s Vulnerability-Hunting Push Signals appeared first on Sazko Solutions.

The problem MCP is actually solving

An AI model is only as useful as the context and actions available to it. Without a shared protocol, every team wiring an agent to Jira, GitHub, a CRM, or an internal database was reinventing the same plumbing, often per model provider. MCP defines a common client-server contract: an MCP server exposes a tool, a resource, or a data source in a standard shape, and any MCP-compatible client — the agent, the IDE, the chat interface — can discover and use it without custom glue code.

Why this matters more than it sounds like it should

Protocols that win are rarely the most powerful option on paper — they win by being boring and universal enough that everyone builds on top of them instead of around them. That’s what happened with HTTP, and it’s the bet being made on MCP for agentic AI: once a tool is exposed as an MCP server, it becomes usable by any compliant agent, not just the one it was originally built for. For an engineering organization, that turns “which AI tool did we build this integration for” into a question that stops mattering.

Where the real work still lives

Adopting MCP doesn’t remove the hard parts of building agents — it relocates them. The protocol tells you how a tool is exposed; it says nothing about whether an agent should be allowed to use it unsupervised, what happens when a tool call fails halfway through a multi-step task, or how you audit what an autonomous agent actually did in production. Teams that treat MCP adoption as “integration solved” tend to skip exactly the governance and observability work that agentic systems need most.

Summary: We see MCP the same way we saw containers a decade ago: not the interesting part of the system, but the part that, once standardized, lets you spend your engineering effort on the parts that actually are.

#AI #MCP #AgenticAI #TechInnovation #SazkoSolutions

Published by Sazko Solutions – Driving Innovation in AI, Agents, and Enterprise Software

The post What MCP Actually Is, and Why It’s Becoming AI’s Common Plumbing appeared first on Sazko Solutions.

Backlog Management

Backlog Management is an essential aspect of agile product management principles. Understanding backlog management helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on backlog management enhances performance, reduces errors, and supports long-term growth.Backlog Management is an essential aspect of agile product management principles. Understanding backlog management helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on backlog management enhances performance, reduces errors, and supports long-term growth.Backlog Management is an essential aspect of agile product management principles. Understanding backlog management helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on backlog management enhances performance, reduces errors, and supports long-term growth.

Prioritization

Prioritization is an essential aspect of agile product management principles. Understanding prioritization helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on prioritization enhances performance, reduces errors, and supports long-term growth.Prioritization is an essential aspect of agile product management principles. Understanding prioritization helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on prioritization enhances performance, reduces errors, and supports long-term growth.Prioritization is an essential aspect of agile product management principles. Understanding prioritization helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on prioritization enhances performance, reduces errors, and supports long-term growth.

Stakeholder Collaboration

Stakeholder Collaboration is an essential aspect of agile product management principles. Understanding stakeholder collaboration helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on stakeholder collaboration enhances performance, reduces errors, and supports long-term growth.Stakeholder Collaboration is an essential aspect of agile product management principles. Understanding stakeholder collaboration helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on stakeholder collaboration enhances performance, reduces errors, and supports long-term growth.Stakeholder Collaboration is an essential aspect of agile product management principles. Understanding stakeholder collaboration helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on stakeholder collaboration enhances performance, reduces errors, and supports long-term growth.

Summary: This blog provides a comprehensive understanding of the topic and practical insights for teams and organizations to implement successfully.

#CloudComputing #Agile #SazkoSolutions #DigitalTransformation #TechInnovation #AI #CloudMigration

Published by Sazko Solutions – Driving Innovation in Cloud, Agile, and AI

The post Agile Product Management Principles appeared first on Sazko Solutions.

From Idea to Product

From Idea to Product is an essential aspect of how sazko builds innovative products. Understanding from idea to product helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on from idea to product enhances performance, reduces errors, and supports long-term growth.From Idea to Product is an essential aspect of how sazko builds innovative products. Understanding from idea to product helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on from idea to product enhances performance, reduces errors, and supports long-term growth.From Idea to Product is an essential aspect of how sazko builds innovative products. Understanding from idea to product helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on from idea to product enhances performance, reduces errors, and supports long-term growth.

Tech Stack Choices

Tech Stack Choices is an essential aspect of how sazko builds innovative products. Understanding tech stack choices helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on tech stack choices enhances performance, reduces errors, and supports long-term growth.Tech Stack Choices is an essential aspect of how sazko builds innovative products. Understanding tech stack choices helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on tech stack choices enhances performance, reduces errors, and supports long-term growth.Tech Stack Choices is an essential aspect of how sazko builds innovative products. Understanding tech stack choices helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on tech stack choices enhances performance, reduces errors, and supports long-term growth.

User-Centric Design

User-Centric Design is an essential aspect of how sazko builds innovative products. Understanding user-centric design helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on user-centric design enhances performance, reduces errors, and supports long-term growth.User-Centric Design is an essential aspect of how sazko builds innovative products. Understanding user-centric design helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on user-centric design enhances performance, reduces errors, and supports long-term growth.User-Centric Design is an essential aspect of how sazko builds innovative products. Understanding user-centric design helps teams implement best practices, improve operational efficiency, and align technical execution with business goals. In practice, organizations should consider tools, processes, and monitoring to ensure optimal outcomes. Real-world examples demonstrate how focusing on user-centric design enhances performance, reduces errors, and supports long-term growth.

Summary: This blog provides a comprehensive understanding of the topic and practical insights for teams and organizations to implement successfully.

#CloudComputing #Agile #SazkoSolutions #DigitalTransformation #TechInnovation #AI #CloudMigration

Published by Sazko Solutions – Driving Innovation in Cloud, Agile, and AI

The post How Sazko Builds Innovative Products appeared first on Sazko Solutions.