The author wrote two fictional texts after their reading volume jumped to roughly 30 novels starting around July 2025. Although the initial 15,000-word piece required seven months to draft, the subsequent 120-page novella was finished in just ten days. To format the books, the author bypassed standard publishing software in favor of groff, utilizing an efficient three-macro setup tailored for basic typography. On a 13.5-year-old computer, this setup rendered the larger document in a mere 1.6 seconds.
Key points
The writer relies on an ancient 13.5-year-old machine that renders the longest manuscript…: The writer relies on an ancient 13.5-year-old machine that renders the longest manuscript in just 1.6 seconds.
A custom typography setup of only three macros was sufficient to format chapters and stan…: A custom typography setup of only three macros was sufficient to format chapters and standard paragraph structures.
Neither of the completed novellas will ever be distributed or published for private or pu…: Neither of the completed novellas will ever be distributed or published for private or public audiences.
Sources checked by our analysis pipeline: 1
blog - git - desktop - contact
2026-10-31
I recently finished my second "novella".
Don't even think about it: I won't publish this. Nor send it to you privately, which is mostly the same as publishing it.
The first story is roughly 50 A5 pages long (~15k words), the second one is about 120 pages (~40k words). (Both barely fit the definition of a "novella", apparently, with the first one being a bit too short and the second one a tiny bit too long.)
It feels pretty absurd and surreal that I have done this at all. In school, anything related to "writing" was pure horror for me -- unless it was related to maths, physics, or other "technical" stuff. But here we are.
How long did it take? Well, the first one took over seven months. But the second one, the longer one? Ten days.
Some time last year, probably around July, I started reading some of the books that were lying around in my appartment for decades. And this was much more enjoyable than I thought. No idea…
The desktop environment's latest cycle expands operating system compatibility by introducing preliminary support for NetBSD. Users gain refined hardware management via integrated network tooling, native PipeWire mixer integration, and unified power controls that align AMD GPU states with CPU profiles. These infrastructural refinements modernize daily workflows while eliminating legacy display configuration options.
Software engineers shifting between these two major ecosystems encounter major friction due to fundamentally divergent design rules for types and object data management. Java mandates strict structure with explicit type declarations inside class bodies, while Python provides a dynamic environment where attributes are created through loosely typed assignments. Understanding these architectural variances prevents programmers from introducing difficult-to-track bugs into their codebases during cross-platform developm…
Software engineers targeting Windows, macOS, and Linux can achieve an authentic native appearance by leveraging a mature framework wrapped around the C++ wxWidgets library. Maintained to modernize the codebase, the toolkit ensures desktop programs blend seamlessly into host operating systems rather than rendering simulated controls. Recent structural updates have also resolved long-standing distribution hurdles, enabling standard automated package installations across supported computing environments.