<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Daniel Oseguera — Journal</title><description>Working notes on backend systems, payments, event-driven architecture and applying AI in production.</description><link>https://danieloseguera.omsoft.com.mx/</link><language>en</language><item><title>AI agents in the dev workflow: where they earn their keep</title><link>https://danieloseguera.omsoft.com.mx/blog/ai-agents-in-the-dev-workflow/</link><guid isPermaLink="true">https://danieloseguera.omsoft.com.mx/blog/ai-agents-in-the-dev-workflow/</guid><description>I run agentic tooling every day. What actually moved delivery speed wasn&apos;t the model — it was the specs, tests and guardrails I wrapped around it. A grounded account, with the parts that still don&apos;t work.</description><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Idempotent payments: retries without the double charge</title><link>https://danieloseguera.omsoft.com.mx/blog/idempotent-payment-retries/</link><guid isPermaLink="true">https://danieloseguera.omsoft.com.mx/blog/idempotent-payment-retries/</guid><description>Retrying a payment is easy. Retrying it safely across a Kafka pipeline is where money actually gets lost. This is the pattern I reach for, and the parts that quietly break it.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate></item></channel></rss>