<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Naviary Tech Blog (English)</title>
  <description>English feed for the Naviary technical archive.</description>
  <link>https://tech.naviary.io</link>
  <language>en-US</language>
  <atom:link href="https://tech.naviary.io/en/rss.xml" rel="self" type="application/rss+xml" />
  <lastBuildDate>Mon, 29 Jun 2026 00:00:00 GMT</lastBuildDate>
  <item>
  <title>Building a Lighthouse on the Sea of AI</title>
  <link>https://tech.naviary.io/en/articles/post/a-lighthouse-in-the-sea-of-ai</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/a-lighthouse-in-the-sea-of-ai</guid>
  <description>A reflection on the domain knowledge and language that keep a project pointed in the right direction, even in an age where AI generates code non-deterministically.</description>
  <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>SOFTWARE DESIGN</category>
  <category>DDD</category>
  <category>Domain-Driven Design</category>
  <category>Ubiquitous Language</category>
  <category>AI</category>
  <category>LLM</category>
  <category>Software Design</category>
  <category>Naviary</category>
</item>
<item>
  <title>Astro. Amaze, Amaze, Amaze</title>
  <link>https://tech.naviary.io/en/articles/post/astro-amaze-amaze-amaze</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/astro-amaze-amaze-amaze</guid>
  <description>Why I chose Astro while rebuilding the tech blog, and how I reviewed the technology stack for it.</description>
  <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>Frontend</category>
  <category>Astro</category>
  <category>Frontend</category>
  <category>Blog</category>
  <category>Static Site</category>
  <category>Naviary</category>
</item>
<item>
  <title>Records, Coordinates, and Direction: Why We Record Technology</title>
  <link>https://tech.naviary.io/en/articles/post/record-coordinate-direction</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/record-coordinate-direction</guid>
  <description>Records become coordinates, and coordinates become direction. This article explains why Naviary, a parrot breeding center, began building a technical archive.</description>
  <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>PHILOSOPHY</category>
  <category>Naviary</category>
  <category>Development Philosophy</category>
  <category>Tech Blog</category>
  <category>Parrot Breeding Center</category>
</item>
<item>
  <title>Naviary System Development #5: Backend - Why My ES Decorator Migration Failed</title>
  <link>https://tech.naviary.io/en/articles/post/naviary-system-05-migration-fail</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/naviary-system-05-migration-fail</guid>
  <description>A brutal migration story I jumped into too quickly because of the word &apos;standard&apos;. This post shares the limitations I ran into and why I ultimately gave up on the migration.</description>
  <pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>BREEDING SYSTEM</category>
  <category>TypeScript</category>
  <category>ES Decorator</category>
  <category>MikroORM</category>
  <category>Dependency Injection</category>
  <category>Migration</category>
  <category>Naviary</category>
</item>
<item>
  <title>What Makes Code Trustworthy?</title>
  <link>https://tech.naviary.io/en/articles/post/what-makes-code-trustworthy</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/what-makes-code-trustworthy</guid>
  <description>Are tests evidence, or comfort? In an age of solo development and AI-assisted coding, what really makes code trustworthy?</description>
  <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>ENGINEERING</category>
  <category>Testing</category>
  <category>TDD</category>
  <category>AI</category>
  <category>Development Philosophy</category>
  <category>Naviary</category>
</item>
<item>
  <title>Naviary System Development #4: Backend - Maximizing Expressiveness with Domain Events</title>
  <link>https://tech.naviary.io/en/articles/post/naviary-system-04-domain-event</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/naviary-system-04-domain-event</guid>
  <description>How to translate the complex flow of the real world into code in the digital world.</description>
  <pubDate>Mon, 23 Feb 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>BREEDING SYSTEM</category>
  <category>Architecture</category>
  <category>DDD</category>
  <category>RxJS</category>
  <category>Domain Events</category>
  <category>Naviary</category>
</item>
<item>
  <title>To DRY or to WET: Live DRY or Stay WET?</title>
  <link>https://tech.naviary.io/en/articles/post/dry-or-wet</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/dry-or-wet</guid>
  <description>When the obsession with perfect abstraction leads to complexity, do we have the courage to choose duplication?</description>
  <pubDate>Thu, 12 Feb 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>ENGINEERING</category>
  <category>DRY</category>
  <category>WET</category>
  <category>Abstraction</category>
  <category>Development Principles</category>
  <category>Naviary</category>
</item>
<item>
  <title>Naviary System Dev Diary #3: Backend - Domain Model Design</title>
  <link>https://tech.naviary.io/en/articles/post/naviary-system-03-design-models</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/naviary-system-03-design-models</guid>
  <description>The process of designing the domain model for Naviary system development.</description>
  <pubDate>Fri, 06 Feb 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>BREEDING SYSTEM</category>
  <category>Naviary</category>
  <category>Bun</category>
  <category>DDD</category>
  <category>Domain Model</category>
  <category>Naviary</category>
</item>
<item>
  <title>Naviary System Dev Diary #2: Backend - Tech Stack</title>
  <link>https://tech.naviary.io/en/articles/post/naviary-system-02-tech-stacks</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/naviary-system-02-tech-stacks</guid>
  <description>The process of choosing the tech stack for Naviary system development.</description>
  <pubDate>Mon, 02 Feb 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>BREEDING SYSTEM</category>
  <category>Naviary</category>
  <category>Bun</category>
  <category>DDD</category>
  <category>Tech Stack</category>
  <category>Backend</category>
</item>
<item>
  <title>Naviary System Dev Diary #1: Why I Chose TypeScript for backend</title>
  <link>https://tech.naviary.io/en/articles/post/naviary-system-01-language-choice</link>
  <guid isPermaLink="true">https://tech.naviary.io/en/articles/post/naviary-system-01-language-choice</guid>
  <description>The language selection process for developing a Naviary system. A summary of how I reviewed and chose a language based on three criteria.</description>
  <pubDate>Wed, 21 Jan 2026 00:00:00 GMT</pubDate>
  <category>en</category>
  <category>BREEDING SYSTEM</category>
  <category>TypeScript</category>
  <category>Language Choice</category>
  <category>DDD</category>
  <category>Tech Stack</category>
</item>
</channel>
</rss>