<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>whatbroke.dev</title>
    <link>https://whatbroke.dev</link>
    <description>What broke. What surprised. What we shipped anyway.</description>
    <language>en-us</language>
    <item>
      <title>When to Stop Adding Ops: The Fallback Case for LLM-Generated Code</title>
      <link>https://whatbroke.dev/site/when-to-stop-adding-ops-the-fallback-case-for-llm-generated-code.html</link>
      <guid isPermaLink="false">whatbroke-6</guid>
      <pubDate>Wed, 24 Jun 2026 21:20:01 +0000</pubDate>
      <description>The Question Should Daytona or E2B.dev fit somewhere in the DCY/Add9 architecture? Initial answer: no. Daytona pivoted from remote dev environments to AI agent sandbox infrastructure — sub 90ms isolated VMs, Python/TS/JS runtimes, snapshot based evals. Our pipeline doesn&#x27;t execute LLM authored code. Our LLMs return structured JSON via stored prompts; Python orchestrates deterministic stages. No…</description>
    </item>
    <item>
      <title>Cron Timezone Drift Made Scheduled Jobs Fight Over the Same Row</title>
      <link>https://whatbroke.dev/site/cron-timezone-drift-made-scheduled-jobs-fight-over-the-same-row.html</link>
      <guid isPermaLink="false">whatbroke-4</guid>
      <pubDate>Sun, 24 May 2026 14:43:33 +0000</pubDate>
      <description>Cron Timezone Drift Made Scheduled Jobs Fight Over the Same Row Scheduled jobs were silently dropping every other run. The pattern was clean: one would succeed, the next would vanish, repeat. Two days to find it. First afternoon was spent in the wrong layer entirely. The assumption was race conditions in the worker code — something racy about how jobs claimed work. Elaborate locking got added…</description>
    </item>
  </channel>
</rss>
