<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on A Field CTO Perspective</title><link>https://gaberger.github.io/categories/ai/</link><description>Recent content in Ai 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/categories/ai/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></channel></rss>