I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline

A novelist-dev just told the internet he walked away from Adobe and Microsoft to build his own book-making system using free tools and version tracking, basically treating a novel like software. On paper, it’s a classic rebel story: one person tired of expensive, clunky publishing workflows decides to stitch together a cleaner, cheaper way to make print books and ebooks. But in the comments, the real plot twist is that readers couldn’t decide whether to applaud, nitpick, or roast him lovingly.

Some were genuinely impressed. One commenter was almost distracted by the fact that the author apparently also wrote multiple Christian historical novels, calling that feat impressive before you even get to the tech side. Another self-publisher jumped in with a battle-scarred “same here,” saying the usual route from Word documents to print and ebook files is a painful mess, especially when tiny edits have to be repeated in multiple places.

Then came the inevitable internet energy: “Um, academics have been doing this forever.” One of the spiciest replies basically framed the whole article as a regular office worker “discovering” old-school computer habits years late. Ouch. Meanwhile, a commercial print veteran pushed back from the opposite angle, arguing the author may be overstating how broken traditional workflows are because pros already know ways to automate much of this.

And yes, there was peak nerd comedy too: a mini side-quest about whether text should use hard wraps or soft wraps, which is the sort of argument that sounds boring until you realize people are passionately debating line breaks like it’s a family feud. In other words, the community verdict is deliciously split: heroic DIY breakthrough or very online reinvention of the wheel?