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.
The blog project has made a major breakthrough. I believe I’ve found the right way to do concurrent development. Next, I’ll finish the first phase: completing Phase A to prove that the path “edit content → new version → publish” can be carried out reliably by a Sonnet-class executor. After that, I’ll look into how to manage the project itself, rather than managing specs and requirements. I believe this is real progress. Now / Next / Later looks like a very simple, actionable way to manage a personal project. I haven’t decided to develop this way yet, but it’s already given me a useful insight. I’m excited about the development process ahead — being able to see the project as a whole, rather than just code and requirements.
Starting with a version that opens and can be read. This blog is where I’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. Taking the first step While building a blog, it’s easy to keep adding things that “should be done before launch”: a better admin backend, a smoother publishing flow, comments, backups, and all kinds of automation. All of that matters, but I also want this to be more than a project that’s forever getting ready. 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. ...