<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Leoblog</title><link>https://douseful.eu.org/en/</link><description>Recent content on Leoblog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://douseful.eu.org/en/index.xml" rel="self" type="application/rss+xml"/><item><title>66,000 Lines of Code, Only 2 Posts Published: A Postmortem of My Blog</title><link>https://douseful.eu.org/en/posts/blog-postmortem/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0800</pubDate><guid>https://douseful.eu.org/en/posts/blog-postmortem/</guid><description>One blog, a little over two weeks, 66,000 lines of code, 24,000 lines of docs, 92 architecture decisions — and in the end, just 2 posts online. The new blog went live on Hugo in two or three minutes. This post lays out exactly where things went wrong.</description></item><item><title>A Major Breakthrough on the Blog Project</title><link>https://douseful.eu.org/en/posts/blog-project-progress/</link><pubDate>Thu, 17 Sep 2026 10:55:24 +0000</pubDate><guid>https://douseful.eu.org/en/posts/blog-project-progress/</guid><description>&lt;p&gt;The blog project has made a major breakthrough. I believe I&amp;rsquo;ve found the right way to do concurrent development. Next, I&amp;rsquo;ll finish the first phase: completing Phase A to prove that the path &amp;ldquo;edit content → new version → publish&amp;rdquo; can be carried out reliably by a Sonnet-class executor.&lt;/p&gt;
&lt;p&gt;After that, I&amp;rsquo;ll look into how to manage the project itself, rather than managing specs and requirements.&lt;/p&gt;
&lt;p&gt;I believe this is real progress. Now / Next / Later looks like a very simple, actionable way to manage a personal project.&lt;/p&gt;
&lt;p&gt;I haven&amp;rsquo;t decided to develop this way yet, but it&amp;rsquo;s already given me a useful insight.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m excited about the development process ahead — being able to see the project as a whole, rather than just code and requirements.&lt;/p&gt;</description></item><item><title>The Blog Is Live</title><link>https://douseful.eu.org/en/posts/hello-world/</link><pubDate>Tue, 15 Sep 2026 09:19:04 +0000</pubDate><guid>https://douseful.eu.org/en/posts/hello-world/</guid><description>&lt;p&gt;Starting with a version that opens and can be read.&lt;/p&gt;
&lt;p&gt;This blog is where I&amp;rsquo;ll record what I learn, practice and think about. Some posts will be polished articles; others may just be notes left behind after solving a problem. Not every entry needs a complete conclusion, but I hope each one leaves something worth coming back to.&lt;/p&gt;
&lt;h2 id="taking-the-first-step"&gt;Taking the first step&lt;/h2&gt;
&lt;p&gt;While building a blog, it&amp;rsquo;s easy to keep adding things that &amp;ldquo;should be done before launch&amp;rdquo;: a better admin backend, a smoother publishing flow, comments, backups, and all kinds of automation.&lt;/p&gt;
&lt;p&gt;All of that matters, but I also want this to be more than a project that&amp;rsquo;s forever getting ready.&lt;/p&gt;
&lt;p&gt;So the first version stays simple: a home page, one post, and static pages that read properly. First give the writing a public home, then let real use decide what to improve next.&lt;/p&gt;</description></item></channel></rss>