<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Adeolu Timothy — Insights</title>
    <link>https://adeolutimothy.com/insights</link>
    <atom:link href="https://adeolutimothy.com/insights/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Whitepapers, industry reports and technical briefs on technology strategy and product architecture.</description>
    <language>en</language>
    <item>
      <title>Designing for Intermittent Infrastructure</title>
      <link>https://adeolutimothy.com/insights/designing-for-intermittent-infrastructure</link>
      <guid isPermaLink="true">https://adeolutimothy.com/insights/designing-for-intermittent-infrastructure</guid>
      <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
      <category>Whitepaper</category>
      <description>Most apps assume the network is there. Across the markets I build for, it usually is not. Here is the architecture I keep coming back to — local-first writes, a durable intent queue, explicit conflict policy, payload budgets — and the parts of it you should skip if you are still looking for product-market fit.</description>
    </item>
  </channel>
</rss>
