Controlled AI-assisted delivery, DevSecOps and compliance engineering, written from inside environments where somebody eventually has to answer for the outcome. 95 posts and counting.
A policy is a document that gets read once by a committee, signed off, and brought out during the post-implementation review when somebody needs to establish whose fault it was. On its own it does nothing, because intent has never stopped anybody. Most of the checking layer in a large organisation exists because somebody wrote down a rule and never built the thing that would make it true.
How do you raise a Copado user story when there is no metadata to deploy, only a script that has to run? The story is still the unit of work. Commit the script to the story branch, let a Function or a manual task execute it, and keep the evidence inside the pipeline where it belongs.
Copado Functions are easy to build and easy to waste. Every execution is a metered container, so the image you pick, the worker you size and the number of times you invoke it are all cost decisions. This is the operating view rather than the build guide.
Google has put an actual spacecraft behind orbital AI compute. The interesting question is not whether a TPU survives launch, it is whether a formation of solar-powered satellites connected by lasers can behave like a data centre. If it can, the first interplanetary civilisation will not announce itself. It will look like a business decision.
The AI infrastructure trade has quietly become a bet on transmission, transformers and construction schedules. Oracle is the clearest case because its numbers make the physical and financial relationship legible. You do not need an AI winter to make the model creak, you just need the grid to behave like an old grid.
DoorDash built a multi-agent LLM system to clean up stale feature flags across 623 repositories. The engineering is genuinely clever. The question nobody asks is why a temporary construct became a population of 60,000. A runtime switch is a migration path or an executable path, and only one of them is allowed to survive.
Google publishes two billion lines of its own code, but the number that should worry you is how little of your product you wrote. Vulnerability submissions rose 263 per cent, NIST has stopped enriching all of them, and mean time to exploit is now negative. What an SBOM is, what one actually looks like, and why a filed one is worthless.
Microsoft shipped fixes for the better part of a thousand vulnerabilities in a single Patch Tuesday, including two already being exploited. That is not a story about Microsoft. It is what an industrial-scale problem discovery mechanism looks like, and it exposes the fact that we have spent thirty years measuring how fast we ship and never once measuring the quality of what arrived.
Five years of running FTP2SF in production showed us that the Lambda layer did not need to carry every byte. Where the provider supports it the browser now streams directly against a signed, narrowly scoped transfer, while Lambda keeps control of authentication, authorisation and orchestration. Plus what we did with the move from Aura to LWC.
Microsoft has shipped an AI tool that reads your Salesforce estate and tells you what to move, change and redesign. That is aimed squarely at the one thing that has always kept customers in place: nobody knows what they have built. A look at the numbers behind the incumbent, the footnotes in the earnings release, and why this fight is different.
Plenty of firms will audit your pipelines and tell you your release process is a liability, while running build pipelines of their own that would not survive the same review. So here are ours with the actual numbers: 21 deployments averaging 82 lines, 29 shared templates, 14 gates that fail the build, and the one that sat written but unwired for weeks.
Merging Salesforce security metadata does not resolve the disagreement between two branches. It just makes the disagreement happen automatically, on the way to production, with nobody watching. Keep an approved Golden Set in its own branch, overwrite the promotion branch before Salesforce sees it, and there is nothing left to merge.
