iTranslated by AI
The Never-Ending Book
I have a habit of reflexively writing posts on Facebook and Twitter, but from now on, I plan to exercise self-restraint by venting my poems here instead.
By the way, on Twitter, @zenn_dev introduced Hiroshi Yuki's "Book."
It seems that various "Books" have already been published.
I spent a long time as a "mercenary," so I'm not very familiar with the current situation. However, back when I was a company employee, there was something called "as-built documents," which referred to the documentation delivered to the client. Even when active on the internet (separately from throwaway diaries or blogs), I used to write articles with these as-built documents in mind. This was the story until about 15 years ago (there's no trace of it since I recently renewed my main site, haha).
But as-built documents become obsolete from the moment you "write" them. Once I realized this, I gave up on the idea of maintaining "as-built documents." After all, it's boring to write them.
It's been five years since I started running a blog with Hugo and GitHub Pages. Unlike old CMSs that discard writing while carrying an RDBMS in the backend, this style seems to suit my nature perfectly. In particular, managing things with git has changed my way of thinking about documentation. There is a way of writing that is neither "as-built documents" nor "throwaway."
Instead of the so-called government-defined e-books, "books" on the internet can commit to the writing process itself and (in some cases) be monetized. And as long as you "keep writing," they don't become obsolete.
The best way to visualize "keep writing" is to keep a history. In that sense, it is correct for Zenn to integrate with GitHub. Furthermore, by making it public on GitHub, readers can easily participate in "keep writing."
In the past, it was said that "software is forever in beta," and documents are also in beta as long as they are "alive." I hope that Zenn will establish itself as an ecosystem for "keep writing."
Discussion