In early September a developer going by Lost Robot released Septabee: a free music workstation for Linux and Windows that he says he built in secret over 20,000 hours. The interface is a node-based dataflow patch. The piano roll is infinite and tunable to any temperament. Modulation is sample-accurate, and you can hang operators on the patch cables themselves. The program is split across isolated processes so that, he claims, it is impossible to fully crash. And then there are the pomegranates — all over the interface, unexplained, bound to the P key, which is also the Z key; the two are equivalent, and no reason is given. You download it from a page on nekoweb that is deliberately awful: it autoplays music and makes you hunt for the clickable region, like it's 1994. His own description of the software is "violently unfinished."

Trace the thing backwards and something more interesting turns up. The earliest version was called Woven Music Studio, thrown together in Code::Blocks and SFML at a point when, by his own account, he had "absolutely no idea what I was doing." After that came rewrite after rewrite from zero. One line he left in his Discord is the whole story: he had written entire DAWs from scratch "over and over and over" — the phrase repeats dozens of times in the actual message — until he had gotten good enough that this one took "just two months of work."

Notice what that means. Each of those discarded DAWs was, in its moment, a complete construct. Not one of them survived. What survived is the part each chisel-pass left behind that the next construct never absorbed — the sediment of rewriting itself. Septabee is not the delivery of a plan; it is the residue of dozens of chisel-construct cycles, named for the first time. Most software buries this stretch of the process: ship the last construct, delete the rest. He keeps the early sketches as a museum inside his Discord, which amounts to leaving the tool marks exposed. That is 余项之美 in its cleanest form — what you can see is not the finished object but the pile underneath it that the finished object did not consume.

"Violently unfinished" is worth taking literally. A finished tool is already-construct: it has a manual, a category, a competitor list, a price. Septabee refuses all four, and not out of modesty — it is holding its own remainder open. Watch how the outside handles that. Writing it up at CDM, Peter Kirn reaches the custom language (not C++ but "B++"), says outright that he doesn't know what to make of it, and afterwards has to publish a correction clarifying what he was and was not claiming. Another gear site runs the thing through a standard review template and files "pricing, platform availability, and release date not yet announced" under drawbacks — for software that is already free and already downloadable. The template doesn't fit. That is not sloppy journalism; there is simply no slot yet for it to sit in.

That vacancy has an expiry date. In a few months it will have a name — "node-based DAW," "FL Studio for weirdos," the first sentence of some encyclopedia entry — and the pomegranates will become brand assets, "violently unfinished" will become copy, and the seam that is open right now will close into one more construct. It will still be a good tool. What will be good is the construct, not the remainder. And one layer of this is only true in 2026: in the same article Kirn complains about the current flood of instantly produced standalone modular tools, so many that opening his inbox gives him a headache. Twenty thousand hours is the one component that cannot be generated. Not because slowness is a virtue, but because those dozens of thrown-away rewrites have no shortcut. They are not in the finished thing. The finished thing grew out of them.

Han Qin (秦汉) · @hqinjarsy · SAE Judgment & Aesthetics