<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Software Architecture and AI on Dan Podina</title><link>https://danpodina.com/log/</link><description>Recent content in Writing on Software Architecture and AI on Dan Podina</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://danpodina.com/log/index.xml" rel="self" type="application/rss+xml"/><item><title>Reviewing AI-Generated Backends: Boundaries, Data, and Failure Modes</title><link>https://danpodina.com/log/reviewing-ai-generated-backends/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://danpodina.com/log/reviewing-ai-generated-backends/</guid><description>&lt;p&gt;&lt;em&gt;The export service below is an illustrative example, not a client case study.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;An AI-built backend can look convincing before anyone has checked how its pieces behave together. Routes exist. Queries return data. A job runs in the background. The useful review question is what happens when a request crosses an ownership boundary or stops halfway through.&lt;/p&gt;
&lt;p&gt;Consider a small SaaS product that exports customer records. A user starts an export, a worker creates a file, and the dashboard offers a download. That one feature crosses authentication, tenant authorization, database access, queue delivery, object storage, and retention.&lt;/p&gt;</description></item><item><title>Entry Point</title><link>https://danpodina.com/log/entry-point/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://danpodina.com/log/entry-point/</guid><description>&lt;p&gt;If you&amp;rsquo;re reading this, you&amp;rsquo;ve scrolled all the way back. This is where it starts.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m Dan. I&amp;rsquo;ve been building software for twenty years — starting from trading floors in Cluj, working my way through CRMs, messaging apps, identity systems, and eventually landing where I am now: architecting clinical data platforms and low-code frameworks.&lt;/p&gt;
&lt;p&gt;This log is a place to think out loud. Some entries will be about code, architecture, or tools I&amp;rsquo;m working with. Others might just be observations about the craft — the kind of things you notice after doing this long enough.&lt;/p&gt;</description></item><item><title>The New Colleagues</title><link>https://danpodina.com/log/new-colleagues/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://danpodina.com/log/new-colleagues/</guid><description>&lt;p&gt;For twenty years, the hard part of this job was people. Not the code — the communication. Sitting in meetings, reading between the lines, figuring out what someone actually needs versus what they&amp;rsquo;re asking for. That takes a specific kind of energy, and after enough of it, you&amp;rsquo;re done for the day.&lt;/p&gt;
&lt;p&gt;Now there&amp;rsquo;s a new presence in the room. Not a person, but not a tool either — something in between. Claude, Gemini, Codex. Pick your flavor. They show up ready, they don&amp;rsquo;t need context repeated, and they&amp;rsquo;re sharp. Genuinely sharp.&lt;/p&gt;</description></item></channel></rss>