<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://nadai.dev/en/feed.xml</id>
  <title>nadai.dev · Writing by Taiki Noda</title>
  <subtitle>Notes on Go backend, pure Go OSS, micro SaaS, and SEO/AIO practice.</subtitle>
  <updated>2026-05-19T00:00:00Z</updated>
  <link rel="self" type="application/atom+xml" href="https://nadai.dev/en/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog"/>
  <link rel="alternate" type="application/atom+xml" hreflang="ja" href="https://nadai.dev/ja/feed.xml"/>
  <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
  <entry>
    <id>https://nadai.dev/en/blog/text-is-the-hard-part</id>
    <title>Reading &apos;native until you need text&apos; as a Pure Go PDF author</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/text-is-the-hard-part"/>
    <published>2026-05-19T00:00:00Z</published>
    <updated>2026-05-19T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">A native developer escaped to a WebView at the text layer. Here is why I refused the same escape route while shipping a Pure Go PDF library.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/antirez-ds4-solo-oss-mode</id>
    <title>What antirez&apos;s DS4 means for a solo Pure Go OSS author</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/antirez-ds4-solo-oss-mode"/>
    <published>2026-05-17T00:00:00Z</published>
    <updated>2026-05-17T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Salvatore Sanfilippo, the Redis author, is shipping DS4 alone — a native local LLM inference engine. What it means for a solo Pure Go OSS author in 2026.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/lean-design-system-for-micro-saas</id>
    <title>Lean design systems as strategy: reading NN/g while running three micro SaaS alone</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/lean-design-system-for-micro-saas"/>
    <published>2026-05-17T00:00:00Z</published>
    <updated>2026-05-17T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">NN/g argues 2-to-5-person design-system teams aren&apos;t a constraint but a strategy. A solo author running three micro SaaS reads it back.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/go-vue3-minimal-stack-template</id>
    <title>Minimal Go + Vue 3 stack template for solo SaaS</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/go-vue3-minimal-stack-template"/>
    <published>2026-05-15T00:00:00Z</published>
    <updated>2026-05-15T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">The Go + Vue 3 stack I actually run for side-project micro SaaS — net/http with slog, Vue 3 + Vite, Firebase Auth, Cloud Run — with the code to match.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/single-binary-distribution-advantage</id>
    <title>Why single-binary distribution wins for solo developers</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/single-binary-distribution-advantage"/>
    <published>2026-05-12T00:00:00Z</published>
    <updated>2026-05-12T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Why single-binary distribution fits solo development on three axes — ops, support, OSS trust — with examples from gpdf and gsql, and where it doesn&apos;t fit.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/mit-first-then-considering-agpl</id>
    <title>Why I&apos;m considering AGPL for the next derived SaaS, after shipping MIT first</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/mit-first-then-considering-agpl"/>
    <published>2026-05-11T00:00:00Z</published>
    <updated>2026-05-11T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Four months after publishing the Pure Go libraries gpdf and gsql under MIT, I&apos;m considering AGPL + CLA + commercial licensing for the next derived SaaS. Nothing in that structure is implemented yet — this is the decision log of a hypothesis, not a methodology.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/show-hn-launch-checklist</id>
    <title>Show HN launch checklist for moonlighting micro SaaS</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/show-hn-launch-checklist"/>
    <published>2026-05-08T00:00:00Z</published>
    <updated>2026-05-08T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">A frontloaded checklist for making Show HN actually reach when you&apos;re moonlighting on a micro SaaS — what to lock in the day before, the first ninety minutes after posting, and how to hand the launch to adjacent communities.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/pre-release-validation-strategy</id>
    <title>Pre-release validation for moonlighting micro SaaS</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/pre-release-validation-strategy"/>
    <published>2026-05-07T00:00:00Z</published>
    <updated>2026-05-07T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">How to narrow your hypotheses before writing code in a moonlighting micro SaaS: a three-layer split, and where to set the threshold for shipping code.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/time-design-of-a-day-job-oss-builder</id>
    <title>Time design: 20 hours a week for OSS alongside a day job</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/time-design-of-a-day-job-oss-builder"/>
    <published>2026-05-06T00:00:00Z</published>
    <updated>2026-05-06T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">How I carve out 20 hours a week for gpdf, gsql, and renma alongside a tech-lead day job: the weekday template, the one-block weekend rule, what gets cut and what does not, and the time I pushed to 30 hours and broke at week 3.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/gsql-api-design-vs-gorm-sqlx-squirrel</id>
    <title>gsql API design: how it differs from GORM, sqlx, and squirrel</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/gsql-api-design-vs-gorm-sqlx-squirrel"/>
    <published>2026-05-05T00:00:00Z</published>
    <updated>2026-05-05T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Releasing yet another Go SQL builder requires a reason. gsql aims for the unoccupied corner: type safety via generics, no code generation, and an explicit answer to Go&apos;s zero-value problem in partial updates.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/nadai-ecosystem-running-multiple-saas</id>
    <title>nadai ecosystem: running multiple micro SaaS as one person</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/nadai-ecosystem-running-multiple-saas"/>
    <published>2026-05-05T00:00:00Z</published>
    <updated>2026-05-05T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">How nadai runs gpdf, gsql, and renma in parallel as a side project: what to share, what to separate, and why the author hub absorbs marketing flow.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/pure-go-micro-saas-on-the-side</id>
    <title>Building Pure Go micro SaaS on the side: where I stand</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/pure-go-micro-saas-on-the-side"/>
    <published>2026-05-04T00:00:00Z</published>
    <updated>2026-05-04T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Working as a tech lead by day, shipping the Pure Go OSS libraries gpdf and gsql under MIT off-hours. Separately building a derived SaaS layer on top of gpdf (gpdf-api and friends) and, on a totally different track, a Flutter weight-training app called renma — none of those released yet. Why MIT first, what I&apos;ve learned, what I&apos;d change next.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/why-pure-go-zero-dependency-pdf</id>
    <title>Building a Pure Go zero-dependency PDF library: gpdf design philosophy</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/why-pure-go-zero-dependency-pdf"/>
    <published>2026-05-04T00:00:00Z</published>
    <updated>2026-05-04T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Why I avoided CGO and wrote gpdf from scratch: the decisions behind a Pure Go, zero-dependency PDF library with native CJK font support.</summary>
  </entry>
  <entry>
    <id>https://nadai.dev/en/blog/gpdf-api-chainable-vs-builder</id>
    <title>gpdf API design: closure-callback builders over method chaining</title>
    <link rel="alternate" type="text/html" href="https://nadai.dev/en/blog/gpdf-api-chainable-vs-builder"/>
    <published>2026-05-04T00:00:00Z</published>
    <updated>2026-05-04T00:00:00Z</updated>
    <author><name>Taiki Noda (野田大貴)</name><uri>https://nadai.dev/en/about</uri></author>
    <summary type="text">Why gpdf&apos;s Go API uses closure-callback builders instead of chainable methods. The design decisions around Go&apos;s error handling, PDF tree structure, and how three different patterns split responsibility cleanly.</summary>
  </entry>
</feed>
