Posts

Agent-Scale Repositories Move the Bottleneck From Git to Engineering Governance

Agent-Scale Repositories Move the Bottleneck From Git to Engineering Governance On 5 November, GitHub described a new Git storage architecture designed for a development model in which thousands of software agents can work on one repository concurrently. In internal testing, GitHub says the system supported 5,000 concurrent agents and 7,200 pushes per second while maintaining low-latency reads. Those numbers are deliberately beyond the needs of almost every engineering organisation today. Their importance is not that teams should attempt to reproduce them. It is that a major software delivery platform is rebuilding its foundations around an expected increase in autonomous, parallel change. If source control can absorb that volume, the constraint moves elsewhere. For engineering leaders, the emerging challenge is no longer whether agents can produce and push code. It is whether the organisation can evaluate, integrate, operate and own the resulting changes safely. Git concurre...

Node.js 26 Is LTS. Runtime Upgrades Must Become an Engineering Capability

Node.js 26 Is LTS. Runtime Upgrades Must Become an Engineering Capability Node.js 26.13.0 entered Long Term Support on 28 October under the codename Lithium. The release line will receive updates until the end of April 2029. That creates a new default for teams starting services and a clear migration target for organisations running older versions. The tempting response is to open an upgrade ticket, assign it to a platform team and treat completion as evidence that the runtime estate is healthy. That misses the more important leadership question: can the organisation move between supported runtimes routinely, without turning every transition into a programme? Runtime currency is not housekeeping. It is an engineering capability that determines how quickly a company can absorb security fixes, adopt framework releases and keep its delivery platform supportable. LTS is a starting signal, not a deadline Node.js 26 becoming LTS does not make Node.js 24 or 22 immediately unsafe. ...

PHP2Shell Is a Test of Whether Your Runtime Estate Is Actually Governed

On 21 October, the PHP project released emergency updates for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both are rated CVSS 4.0 at 9.2 and can allow unauthenticated remote code execution. The project's guidance is unusually direct: there are no complete mitigations, and updating is the only safe choice. Patched releases are available for supported PHP 8.2, 8.3, 8.4 and 8.5 branches. The incident is already being called PHP2Shell, but the strategic lesson is not about the nickname or the exploit mechanics. It is about whether an engineering organisation can identify, patch and prove the state of every production runtime under urgent conditions. A version number is not an estate inventory Leaders often ask, "Which PHP version do we run?" and receive a reassuring single answer. Real estates are rarely that simple. The production runtime may appear in container base images, serverless layers, build agents, command-line workers, scheduled jobs,...

Open-Source Licensing Is Moving Into the Merge Gate

On 16 October, GitHub made open-source licence compliance generally available for GitHub Enterprise Cloud repositories using GitHub Code Security. The capability allows enterprises to define a central licence policy, apply it through repository rulesets and block pull requests when new or changed dependencies do not comply. This is more than another supply-chain control. It shifts licence management from periodic audit into the daily engineering workflow. Licence risk has traditionally arrived too late Many organisations discover licensing problems during procurement, a customer due-diligence exercise, an acquisition or a release audit. By then, an unsuitable dependency may be deeply embedded in the product. Replacing it can require architectural work, retesting and an awkward conversation about why the issue was not identified earlier. The failure is rarely that engineers ignored policy. More often, the policy lived in a legal document, spreadsheet or specialist scanning too...

Stacked Pull Requests Are Now Mainstream. Your Review Model Needs to Catch Up

On 6 October, GitHub made stacked pull requests generally available. The feature allows engineers to break one substantial change into a sequence of dependent pull requests, review each layer independently and merge all or part of the stack while preserving the dependency order. This sounds like a workflow convenience. For engineering leaders, it is more consequential. Pull request size is one of the quiet variables shaping delivery speed, review quality and operational risk. Stacks offer a way to reduce batch size without forcing engineers to wait for every intermediate change to reach the main branch. Used well, they can shorten feedback loops and make architectural intent easier to review. Used badly, they can turn one opaque change into five interdependent queues. The problem is not large pull requests alone Most teams already know that large pull requests are difficult to review. The reviewer must reconstruct more context, defects hide amongst mechanical changes and feedba...

npm Closed the Last Token Gap in Trusted Publishing. Now Remove Your Release Secrets

On 30 September, GitHub and npm removed a small but important obstacle to token-free package publishing. npm trusted publishing configurations can now receive an opt-in permission to manage distribution tags such as latest , next and beta using short-lived OpenID Connect credentials. The feature will not dominate technology headlines. It should nevertheless prompt an immediate review in organisations that publish JavaScript packages. Until now, teams could use trusted publishing for the release itself, yet still need a long-lived npm access token to promote a staged version, move a prerelease channel or perform a rollback by changing a tag. One residual secret was enough to preserve a material attack path. The real change is the trust model Traditional release automation starts with a stored credential. A person creates an npm token, places it in a CI secret store and relies on process controls to keep it valid, scoped and rotated. The workflow presents that bearer token to n...

Your Source Code Is Now an AI Data-Boundary Decision

On 21 September, Belgian security company Aikido released an open-weight model designed for cybersecurity work that can run locally, without sending source code to an external model provider. The announcement is one product release, but the underlying question is becoming strategic for every software organisation using AI: where is your code allowed to go? Engineering leaders have spent years classifying customer data, production credentials and regulated records. Source code has often received less precise treatment. It may be private, but it is routinely copied into local tools, build systems, SaaS scanners, support tickets and now AI assistants. As AI becomes part of development and security workflows, that ambiguity is no longer sustainable. The decision is not simply whether cloud AI is safe or local AI is better. It is about choosing an execution boundary that matches the sensitivity of the code, the capability required and the controls the organisation can genuinely operate. ...

The Four Horsemen of Software Development

Most engineering teams are described through seniority, discipline or reporting lines. We count frontend developers, backend developers, platform engineers, Staff Engineers and Engineering Managers. Those labels are useful for organisation design, but they say surprisingly little about how a team actually creates value. A more revealing view is to look at the forces engineers bring to the software lifecycle. Healthy teams need four of them: discovery, delivery, protection and renewal. Think of the people who naturally lead those forces as the Four Horsemen of Software Development: the Pathfinder, the Builder, the Guardian and the Steward. These are not fixed personality types, and nobody should receive one as a permanent label. Strong engineers can operate in several modes. The framework is useful because it exposes imbalance. Many teams have plenty of Builders but no Steward, or a powerful Guardian who is engaged only when a release is already in trouble. 1. The Pathfinder The Pat...

Chrome Now Ships Every Two Weeks. Your Web Release Process Must Catch Up

Chrome 154 entered the stable channel on 22 September 2026. On its own, that is a routine browser update. What makes it strategically important is that it marks the operating reality of Chrome's new two-week release cycle, replacing the four-week milestone cadence that has existed since 2021. Google's stated rationale is reasonable: smaller releases, faster access to platform improvements and a shorter gap between fixes becoming available and reaching users. Chrome 154 also contains 108 security fixes, illustrating why browser vendors want the ability to move quickly. For web engineering organisations, however, doubling the frequency of stable milestones changes more than a calendar. It compresses the time available to detect compatibility risks, validate critical journeys and respond before a change reaches a large percentage of customers. The wrong response is to double the amount of manual regression testing. The right response is to redesign browser compatibility as a con...

Your Delivery Platform Is Tier-Zero Infrastructure

On 10 September, GitLab released critical patches for its Community and Enterprise editions. The most serious issue, CVE-2026-85706, was assigned a CVSS score of 10.0. Under certain conditions, an unauthenticated attacker could use the repository commits API to read arbitrary files from a GitLab server. One day later, the US Cybersecurity and Infrastructure Security Agency added the vulnerability to its Known Exploited Vulnerabilities catalogue based on evidence of active exploitation. The immediate response is straightforward: affected self-managed installations should be upgraded to GitLab 19.1.8, 19.2.6, 19.3.2 or later, and potentially exposed systems should be investigated rather than treated as safe simply because a patch has now been applied. The more important leadership lesson is broader. Source-control and delivery platforms are no longer developer tools at the edge of the estate. They are tier-zero infrastructure: systems whose compromise can provide a route into much of t...

AI Coding Agents Are Becoming an Engineering Management Problem

This week’s $200 million funding round for enterprise coding-agent company Factory, reportedly valuing the business at $5 billion, is another sign that AI-assisted development is moving beyond autocomplete. The emerging product is no longer simply a faster way to write a function. It is an agent capable of reading a codebase, planning changes, editing several files, running tests and preparing work for review. For web developers, that shift is significant. Modern applications contain far more than JavaScript components: infrastructure configuration, analytics, accessibility rules, automated tests, deployment pipelines and security controls all sit within the same delivery system. An agent that can reason across those boundaries may remove hours of repetitive work. Dependency upgrades, test scaffolding, documentation, migration preparation and first-pass bug fixes are increasingly realistic candidates for delegation. But the more interesting challenge belongs to engineering managers. ...

The road to CAIO

The Engineer Who Stops Owning Only the Code For much of a software engineer’s career, progression appears straightforward. Junior Developer. Developer. Senior Developer. Perhaps Staff or Principal Engineer. Engineering Manager. Head of Engineering. CTO. Artificial intelligence has introduced another destination: Chief AI Officer — CAIO . At first glance, it seems like a role intended for machine-learning researchers, data scientists and people who have spent their careers building neural networks. That assumption misses what may become one of the most important aspects of the role. A successful CAIO does not necessarily need to be the person who can build the best model. They need to be the person who can answer a much bigger question: How should this organisation use AI to become better? That creates an interesting career opportunity for experienced software engineers. The journey from Senior Developer to CAIO isn't about abandoning engineering. It is about repeatedly wi...

Your Roadmap Is Wrong Until It Includes Hidden Engineering Work

Most engineering roadmaps begin with visible product outcomes and then allocate people as though every available day can be converted into feature delivery. The plan looks credible until incidents, support, maintenance, onboarding, security updates and cross-team dependencies consume the capacity that was never acknowledged. This is often described as unexpected work. Much of it is entirely predictable. The uncertainty lies in timing and volume, not in whether it will exist. Capacity is not headcount A team of six does not provide six full-time units of roadmap capacity. People attend planning, reviews, one-to-ones and organisational work. They take leave, support colleagues, respond to production and maintain existing services. Specialists may create constraints that average headcount conceals. Start with historical evidence. Review how time was actually spent across several months: planned product work, operational support, defects, platform maintenance, discovery and unpla...

Architecture Guardrails Beat Architecture Permission

As engineering organisations grow, leaders often create architecture review boards to prevent inconsistency and costly mistakes. The intention is sound. The failure mode is predictable: decisions queue behind a small group, teams prepare presentation theatre and reviewers become accountable for systems they do not operate. The alternative is not architectural anarchy. It is to replace broad permission with clear guardrails, local ownership and deliberate escalation for genuinely consequential decisions. Define the safe operating space Guardrails describe the boundaries within which teams can decide independently. They might cover identity, encryption, data classification, observability, supported runtimes, public API standards and operational ownership. A good guardrail is testable and connected to a risk. "Use approved technology" is vague. "Customer credentials must be stored in the managed secrets service and never exposed to build logs" provides an enf...

Blameless Incidents Still Need Clear Accountability

Blameless incident management is sometimes misunderstood as avoiding judgement. In a healthy engineering organisation, it means removing fear and hindsight bias so the system can be examined honestly. It does not mean that ownership, standards or follow-through disappear. An incident review that concludes "the process failed" without identifying who will change the process is not blameless. It is incomplete. Separate fault from accountability Fault asks who caused the event. Accountability asks who owns the response, learning and risk decision. Individuals can make reasonable choices within a system that produces a poor outcome. The organisation still needs named people responsible for restoring service, communicating impact and ensuring agreed improvements happen. This distinction encourages disclosure. Engineers should be able to explain exactly what they did and believed without fearing punishment for an honest mistake. Leaders, in turn, must be able to require s...