<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Danilo Falcão da Silva</title><link>https://falcao.org/tags/productivity/</link><description>Recent content in Productivity on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 21 May 2026 07:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Notion vs Obsidian: Local-First Sounds Great Until You Have to Sync It</title><link>https://falcao.org/posts/notion-vs-obsidian/</link><pubDate>Thu, 21 May 2026 07:00:00 -0300</pubDate><guid>https://falcao.org/posts/notion-vs-obsidian/</guid><description>&lt;p>I configure infrastructure for a living. Containers, reverse proxies,
NFS mounts, certificate renewals, sync layers between machines —
that&amp;rsquo;s most days. The last thing I want when I open my personal
note-taking app is &lt;strong>another sync layer to babysit.&lt;/strong> That, more than
anything else, is why I picked Notion over Obsidian.&lt;/p>
&lt;p>This is the honest read on &lt;strong>Notion vs Obsidian&lt;/strong> for one person, one
phone, one Linux desktop, and the occasional browser tab on someone
else&amp;rsquo;s machine. The headline: &lt;strong>Obsidian is the purer architecture
and the wrong fit for me. Notion is the lazy architecture that does
the right thing without asking.&lt;/strong> For a personal knowledge base, lazy
wins.&lt;/p></description></item></channel></rss>