AI agent payments have produced four competing specifications, two industry foundations and an enormous amount of coverage in about a year. What they have not yet produced, for the overwhelming majority of merchants, is revenue. The gap between the noise and the numbers is the useful part to understand, because the...
Automation
Articles, guides and tutorials on software automation, covering CI/CD pipelines, test automation and workflow automation for development teams.
Agentforce is priced by consumption, and that single fact should change how you budget for it. Most Salesforce buyers arrive with a seat-licence mental model, ask what an agent costs per user per month, and get a number that does not describe their bill. The bill is a function of how many actions the agent takes, and...
A salesforce integration almost never fails on protocol. Authenticating is a solved problem and posting a record is a solved problem. What ends projects is the daily request allocation and the shape of the data model, both usually discovered about three weeks after go-live, when the nightly job starts returning errors...
A postmortem is easy to hold and hard to make useful. The meeting happens, a document is written, four action items are recorded, and six months later the same failure occurs and somebody finds the old document while searching for something else. The word “blameless” gets most of the attention in discussions of this,...
Supply chain security sounds like a problem for organisations with a security function, and the framing is misleading. A small team running a handful of services typically depends on hundreds of packages it has never read, pulled at build time from registries it does not control, executing installation scripts on...
Technical documentation fails in a specific and predictable way. Somebody writes a great deal of it during a quiet fortnight, the system changes, nobody updates it, and within a year the document is confidently wrong. At that point it is worse than nothing, because a reader who trusts it acts on information that no...
Developer onboarding is usually measured in how long the induction takes, which is the wrong end of the problem. The number that matters is how long before a new engineer can change something and be confident they have not broken anything else, and in most teams that is measured in months rather than days. The delay is...
An uptime SLA looks like a promise and behaves like a refund policy. Suppliers know this. Customers frequently do not, and sign a service level agreement believing they have bought availability when what they have bought is a small discount in the event they do not get it. That is not necessarily a bad deal. It is a...
Disaster recovery in a small team is usually one line in a document nobody has opened: backups are enabled. That statement is true and it is not an answer, because it says nothing about how old the data would be, how long the restore takes, or whether anyone has ever performed one. The gap between having backups and...
Software testing strategies are usually described in terms of coverage, and coverage is the least informative number in the whole discipline. A codebase at ninety per cent can ship a bug on its most-used path, because coverage measures which lines executed during a test run, not whether anything meaningful was asserted...