<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agentic-Engineering on aeshift</title>
    <link>https://aeshift.com/tags/agentic-engineering/</link>
    <description>Recent content in Agentic-Engineering on aeshift</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&amp;copy; 2026 [Dachary Carey](https://dacharycarey.com) - with agent assistance · Part of the [Agent Ecosystem Research Program](https://agentecosystem.dev)</copyright>
    <lastBuildDate>Tue, 03 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aeshift.com/tags/agentic-engineering/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Synthesized, Not Engineered</title>
      <link>https://aeshift.com/posts/2026-03-03-synthesized-not-engineered/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aeshift.com/posts/2026-03-03-synthesized-not-engineered/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a paper out of Cornell this week that should make you uncomfortable if you build general-purpose software systems for a living.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://arxiv.org/abs/2603.02081&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;GenDB&lt;/a&gt; takes a simple, almost reckless-sounding premise: what if you replaced your database&amp;rsquo;s query execution engine with an agentic system that writes fresh, custom C++ code for every single query? No fixed operator set. No general-purpose execution model. Just an LLM that looks at your query, your data, and your hardware, then synthesizes exactly the program needed to answer it.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://aeshift.com/posts/2026-03-03-synthesized-not-engineered/feature.jpg" />
    </item>
    
    <item>
      <title>A TeX Chess Engine Isn&#39;t a Trick; It&#39;s What Agents Do Under Constraint</title>
      <link>https://aeshift.com/posts/2026-02-28-coding-agents-wrote-a-chess-engine-in-pure-tex/</link>
      <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aeshift.com/posts/2026-02-28-coding-agents-wrote-a-chess-engine-in-pure-tex/</guid>
      <description>&lt;p&gt;You shouldn&amp;rsquo;t read the &amp;ldquo;chess engine in pure TeX&amp;rdquo; stunt as a party trick. You should read it as a warning shot. Coding agents are now good enough at &lt;em&gt;systems thinking under hostile constraints&lt;/em&gt; that your bottleneck is shifting from &amp;ldquo;can the agent write code&amp;rdquo; to &amp;ldquo;can you give it guardrails, tests, and observability before it invents a tiny virtual machine inside your build.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://blog.mathieuacher.com/TeXCCChessEngine/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Mathieu Acher&amp;rsquo;s write-up&lt;/a&gt; tells the whole story.&lt;/p&gt;</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://aeshift.com/posts/2026-02-28-coding-agents-wrote-a-chess-engine-in-pure-tex/feature.jpg" />
    </item>
    
  </channel>
</rss>
