<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A Field CTO Perspective</title><link>https://gaberger.github.io/</link><description>Recent content on A Field CTO Perspective</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gaberger.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside the AI Harness: The Substrate Around the Chat</title><link>https://gaberger.github.io/2026/10/inside-the-ai-harness/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/10/inside-the-ai-harness/</guid><description>&lt;p>&lt;em>Written by a practitioner who has spent three years building AI apps, harnesses and code development tools. See&lt;/em> About the author &lt;em>at the end.&lt;/em>&lt;/p>
&lt;h2 id="why-the-harness-matters">Why the harness matters&lt;/h2>
&lt;p>In 2026, what an AI agent can actually do depends less on the model and more on the software wrapped around it. That wrapper is the harness.&lt;/p>
&lt;p>A language model on its own is a function: text in, text out. It cannot read a file, run a test, remember yesterday, or check its own work. Everything that lets it do those things lives outside the weights.&lt;/p></description></item><item><title>The Rules Nobody Wrote Down</title><link>https://gaberger.github.io/2026/09/the-rules-nobody-wrote-down/</link><pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/09/the-rules-nobody-wrote-down/</guid><description>&lt;p>&lt;em>For twenty years, good software depended on people remembering which parts of a program were allowed to talk to which. AI coding tools don&amp;rsquo;t remember. So the rule has to be written down where a machine can enforce it.&lt;/em>&lt;/p>
&lt;p>A growing share of new code is written by AI. &lt;a href="https://arxiv.org/abs/2506.08945v2">One peer-reviewed study&lt;/a> estimates that by early 2025 about 29 percent of new Python functions pushed to GitHub from the United States were AI-written, the highest rate the study measured, up from about 5 percent in 2022.&lt;/p></description></item><item><title>The deterministic half of neuro-symbolic AI already exists. It's called network verification.</title><link>https://gaberger.github.io/2026/07/deterministic-half-of-neuro-symbolic-ai/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/07/deterministic-half-of-neuro-symbolic-ai/</guid><description>&lt;p>Everybody&amp;rsquo;s suddenly got a take on neuro-symbolic AI. Inference for pattern recognition, symbolic logic paired in for reasoning you can actually trust, and the EU AI Act&amp;rsquo;s enforcement phase lighting a fire under all of it because &amp;ldquo;the model said so&amp;rdquo; stopped being an acceptable audit trail.&lt;/p>
&lt;p>The pitch is real. Inference is powerful and unreliable, a statistical guess dressed up as an answer. Deterministic, mathematical models are reliable and narrow. Combining them, having the deterministic side check inference&amp;rsquo;s work, is turning into the actual path to AI you can trust in production. What&amp;rsquo;s less talked about: in networking, the deterministic half of that equation isn&amp;rsquo;t something you&amp;rsquo;d have to build. It already exists, and it&amp;rsquo;s been hardening in production for 7 years.&lt;/p></description></item><item><title>Delivering APIs for AI</title><link>https://gaberger.github.io/2026/07/delivering-apis-for-ai/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/07/delivering-apis-for-ai/</guid><description>&lt;p>The rise of AI agents and autonomous systems is fundamentally changing how we design and deliver APIs, shifting from human-centric interfaces to AI-native integration patterns that require new architectural thinking.&lt;/p>
&lt;h3 id="the-inflection-point">The Inflection Point&lt;/h3>
&lt;p>Technology innovation has repeatedly transformed how we build systems. From the fourth-generation programming languages (4GL) of the 1990s that abstracted database operations to today&amp;rsquo;s AI-powered code generation, each wave has forced us to rethink fundamental assumptions. We now stand at another such inflection point: the transition from human-interface (HI) APIs to agent-interface (AI) APIs.&lt;/p></description></item><item><title>Breaking the Capability Trap</title><link>https://gaberger.github.io/2026/06/breaking-the-capability-trap/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/06/breaking-the-capability-trap/</guid><description>&lt;h2 id="a-systems-approach-to-safe-fast-network-change">A Systems Approach to Safe, Fast Network Change&lt;/h2>
&lt;p>A whitepaper on applying System Dynamics to network change management, and the business case for pre-change simulation&lt;/p>
&lt;h2 id="executive-summary">Executive Summary&lt;/h2>
&lt;p>Network change is one of the riskiest things an enterprise does to itself. A single routing or firewall edit can quietly break an application dependency, pull reachability from a whole region, or take the business offline for hours.&lt;/p>
&lt;p>The usual response (freezes, heavier approval boards, rarer maintenance windows) feels like risk reduction but isn&amp;rsquo;t. Research from MIT Sloan&amp;rsquo;s System Dynamics group shows it does the opposite. Each control added after a failure quietly raises the odds of the next one, and the organization spends years tightening the loop on itself.&lt;/p></description></item><item><title>A brief look at Network Automation</title><link>https://gaberger.github.io/2017/06/a-brief-look-at-network-automation/</link><pubDate>Tue, 06 Jun 2017 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2017/06/a-brief-look-at-network-automation/</guid><description>&lt;p>There is an incredible amount of hype these days discussing automation especially in the realm of networking. Some would say that this is relatively new but I would argue that we have been struggling with automating the network for many decades, it is however becoming critical today due to the massive dependencies on our communications facilities and shifting application architectures towards distributed computing.&lt;/p>
&lt;p>As defined by Oxford the definition of automation:&lt;/p></description></item><item><title>Monitoring the Control Plane</title><link>https://gaberger.github.io/2017/05/monitoring-the-control-plane/</link><pubDate>Sun, 28 May 2017 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2017/05/monitoring-the-control-plane/</guid><description>&lt;h2 id="primer">Primer&lt;/h2>
&lt;p>Within every customer, provider and transport network, there exists a host of applications that collect, disseminate and make decisions so that application services can communicate. These applications are also known as routing protocols and are at the core of how the Internet functions. The most common routing protocols used today include: Border Gateway Protocol (BGP) ₁, Open Shortest Path First (OSPF)₂ and IS-IS (Intermediate System - Intermediate System) ³.&lt;/p></description></item><item><title>Facebook Fabric Networking Deconstructed</title><link>https://gaberger.github.io/2013/01/facebook-fabric-networking-deconstructed/</link><pubDate>Mon, 28 Jan 2013 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2013/01/facebook-fabric-networking-deconstructed/</guid><description>&lt;p>Facebook engineering has recently introduced their next-generation data center network architecture planned to be operational in the new Altoona facility. &lt;a href="https://code.facebook.com/posts/360346274145943/introducing-data-center-fabric-the-next-generation-facebook-data-center-network">Introducing data center fabric, the next-generation Facebook data center network&lt;/a>&lt;/p>
&lt;p>In this post we are going to look at the design proposed and break down some of the reasons why this design was necessary although maybe still not ideal.&lt;/p>
&lt;hr>
&lt;h2 id="facebook-the-killer-app-literally">Facebook, the killer app.. literally&lt;/h2>
&lt;p>Within Facebook’s data center the network is a critical component driving this social networks ever increasing appetite to connect people together. The challenges unfold on two axis, the first being the explosive growth in the user population and its increasing demand and access bolstered by modern mobile devices and the second related to the exponential growth of machine to machine traffic required to aggregate and compose information which we all know and love. Due to the nature of Facebook applications, machine to machine communications is “several orders of magnitude larger than what goes out the Internet”&lt;/p></description></item><item><title>About</title><link>https://gaberger.github.io/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/about/</guid><description>&lt;p>Gary Berger is a Field CTO and principal engineer. He writes about network
automation, control-plane observability with eBPF, and data center fabric
design.&lt;/p>
&lt;p>Developer, engineer, father, musician.&lt;/p></description></item><item><title>AI Research Index</title><link>https://gaberger.github.io/ai-research/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/ai-research/</guid><description>&lt;p>Open-source AI projects I&amp;rsquo;m tracking, grouped by area: local inference on owned hardware, multi-agent orchestration, coding agents, memory and reasoning, agent tooling, and agent sandboxes.&lt;/p></description></item><item><title>Experiments</title><link>https://gaberger.github.io/experiments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/experiments/</guid><description>&lt;p>Smaller things I&amp;rsquo;ve tried in the open: prototypes, workshop repos and ideas
that may or may not grow up. The finished work is on the
&lt;a href="https://gaberger.github.io/projects/">Projects&lt;/a> page.&lt;/p></description></item><item><title>Projects</title><link>https://gaberger.github.io/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/projects/</guid><description>&lt;p>Some of the things I&amp;rsquo;ve built and put in the open, mostly tools for working with
AI agents, APIs and networks. Everything else is on
&lt;a href="https://github.com/gaberger">GitHub&lt;/a>.&lt;/p></description></item></channel></rss>