<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sassi M., frontend architecture notes</title>
    <link>https://msassi.dev/insights/</link>
    <atom:link href="https://msassi.dev/rss.xml" rel="self" type="application/rss+xml" />
    <description>Remote senior frontend developer and React consultant, based in Toronto. I build first versions and repair hard-to-change React and TypeScript frontends for product teams across Canada and the US.</description>
    <language>en-CA</language>
    <item>
      <title>Shared React Components Need Migration Boundaries</title>
      <link>https://msassi.dev/insights/shared-react-components-need-migration-boundaries/</link>
      <guid isPermaLink="true">https://msassi.dev/insights/shared-react-components-need-migration-boundaries/</guid>
      <description>What I learned moving form and table behavior across separate healthcare applications without turning a component library into an internal framework.</description>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <category>Frontend architecture</category>
    </item>
    <item>
      <title>Replacing React Router With Wouter Without Breaking Auth Flows</title>
      <link>https://msassi.dev/insights/replacing-react-router-with-wouter-without-breaking-auth-flows/</link>
      <guid isPermaLink="true">https://msassi.dev/insights/replacing-react-router-with-wouter-without-breaking-auth-flows/</guid>
      <description>What changed when I replaced the router across two React applications, and why the important work was preserving layouts, deep links, and post-login redirects.</description>
      <pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate>
      <category>Frontend architecture</category>
    </item>
  </channel>
</rss>
