So, remember that massive infinity poem I recently announced? The one containing 7,007,317 words, 561,009 lines, 156,640 paragraphs, and 15,345 pages? Yeah. Well, there is another side to this whole project that deserves its own post. Because while the final numbers might be impressive, getting this enormous thing to the point where I could actually share it with the world has been a logistical nightmare in its own right. And when I say nightmare, I mean that this project has tested practically every tool, program, website, and service I’ve tried to use along the way. Microsoft Word has been tested. WordPress has been tested. Google Docs has been tested. Free online file converters have been tested. My patience has been tested. And at various points, it has felt like the entire technological ecosystem was collectively asking me what the hell I thought I was doing.
When I started this project, I knew that creating something this large would eventually cause problems. I wasn’t under the illusion that I could casually produce millions of words, throw everything into a document, click a button, and have the entire thing work perfectly. I understood that there would be limits. Programs have memory limitations. Websites impose upload restrictions. File converters have their own constraints. Documents become increasingly unwieldy as they grow. And when you’re dealing with a manuscript containing more than seven million words, you’re no longer operating at the scale most ordinary writing tools are designed to handle comfortably. I expected technical difficulties, and I accounted for the possibility that things would go wrong. What I didn’t necessarily know was exactly how many different things would decide to become a problem.
Microsoft Word was one of the biggest parts of this experience. It is a program people use every day to write essays, reports, books, and all kinds of other documents. But there is a difference between writing a normal document and assembling a poetic manuscript that stretches across 15,345 pages. At that point, you’re asking a familiar writing program to manage something that is far outside the ordinary experience of most users. Working with the document, navigating it, processing it, and trying to make sure everything remains intact become challenges in themselves. A program that feels perfectly comfortable with a short essay can become a very different beast when the document grows to this scale. Suddenly, the question isn’t just whether I can write more. It is whether the tools I’m using can continue to handle what I’ve already written.
Then there was WordPress. Since I wanted to share this project with readers of Musings of Jaime David, I had to think about how the manuscript would actually be made available. It is one thing to publish an ordinary blog post. It is another thing entirely to figure out how to distribute a document containing millions of words without turning the blog itself into an enormous technical headache. WordPress has its own practical limitations, including media upload restrictions, available storage, and the difference between publishing a post and hosting a gigantic document for readers to access. I had to consider what would work, what would not, and how to make the manuscript available without forcing the entire project into a format that wasn’t designed for it.
And then there was Google Docs. Initially, I thought it would be a convenient way to host the complete manuscript. It seemed like a straightforward solution: put the document online, share a link, and let people access the poem. Simple enough. Except there was one fairly significant problem. The document was too large. Google Docs wasn’t a workable option for hosting the complete manuscript in the way I needed, so I had to abandon that plan and look for an alternative. Imagine putting all this effort into assembling a seven-million-word poem, only to discover that one of the most familiar document-sharing services wasn’t going to be the solution. At that point, I had to stop and reconsider how I was going to distribute the thing.
Then came the file converters. Oh, the file converters. If you’ve ever searched online for a free tool to convert a Word document into a PDF, you probably know that there are plenty of websites promising to make the process easy. Upload a file, click a button, wait a moment, and download the result. Simple enough, right? Well, that simplicity starts to become questionable when your document is thousands of pages long and contains millions of words. A tool that works perfectly well for an ordinary document might struggle with a file of this size. Some processes can become painfully slow, others can run into limitations, and sometimes the result simply isn’t what you expected. I had to confront the reality that not every tool advertised as a convenient solution is equipped to handle the sort of experiment I was conducting.
There were moments when things glitched out, processes failed, and tools behaved in ways that made the whole experience even more frustrating. Some of the things I tried did not work as intended, and there were times when it felt as though I was pushing software beyond what it had been designed to do. I don’t want to exaggerate the technical details or pretend that every failure had the same cause. Different programs have different limitations, and not every problem can be reduced to one simple explanation. But the overall experience made one thing very clear: creating the manuscript was only part of the challenge. Figuring out how to preserve it, convert it, store it, and distribute it was another challenge entirely.
Eventually, I settled on Dropbox. After Google Docs proved unsuitable for the full manuscript, I needed a practical way to share the files without trying to publish millions of words directly on WordPress. Dropbox gave me a way to share the manuscript through a folder link, which meant I could direct readers to the files rather than force the entire project into a traditional blog post. Was it the original plan? No. Was it the route I expected to take when I started this whole thing? Not necessarily. But it gave me another option, and at this stage, finding a workable solution mattered more than sticking stubbornly to my first idea. The objective was to get the poem into a form that people could access, and I was willing to change course to make that happen.
The funny thing is that none of this really surprised me. I knew there would be obstacles. I knew that producing something this enormous would eventually force me to confront the practical limitations of the tools I was using. I knew that I would probably have to change my approach, try different methods, and accept that certain things would not work the way I wanted them to. In a sense, that was part of the experiment. I wasn’t merely trying to create a long poem. I was also discovering what happens when you use ordinary digital tools to handle a project that has grown far beyond ordinary proportions. I wanted to find out how far I could take it, and that meant finding out where the friction started.
And yes, there were times when I got frustrated. It would be ridiculous to pretend otherwise. When you have put so much effort into a project, the last thing you want is to get stuck trying to convert a file or work around an upload restriction. You want to share the finished result, not spend your time troubleshooting the software that is supposed to help you share it. But that is the reality of undertaking something unusual. You can have the idea, generate the material, assemble the manuscript, and reach your final word count, only to discover that the final stages involve a completely different set of problems. The creative process and the logistical process are connected, but they are not the same thing.
Still, I pushed through. I kept trying different approaches, reconsidered how I would distribute the manuscript, and eventually found a way to share it through Dropbox. The goal was not to find the most complicated method possible. It was to find a reliable way to make the manuscript accessible to readers. If one method turned out to be impractical, I could investigate another. If a particular tool could not handle the document, that did not automatically mean the project itself had to stop. Google Docs didn’t work out for the complete manuscript, but that didn’t mean I had to give up on sharing it.
There is an important distinction here: I didn’t set out to break software for the sake of breaking it. I wasn’t trying to cause trouble for the companies that created these tools, and I wasn’t trying to prove that every program was inadequate. I was pursuing a creative project and testing the limits of the tools available to me in the process. Those are different things. The fact that I encountered technical problems doesn’t mean the tools are bad at what they ordinarily do. Microsoft Word, WordPress, Google Docs, and file converters serve different purposes and operate under different constraints. They are not necessarily designed around the idea that someone will try to manage a seven-million-word poem. My project was unusual, and it exposed limitations that might never matter to someone working on a more conventional document.
But that is precisely what made the experience interesting. Sometimes, you don’t discover the boundaries of a tool until you attempt something that pushes against them. You can read specifications, learn about file-size limits, and understand the general capabilities of a program, but actually working on an unusually large project gives you a different perspective. You discover which parts of the process are easy, which parts are difficult, and which assumptions stop being useful once the scale changes. In my case, the experiment extended beyond the poem itself. It became an exercise in problem-solving, persistence, and figuring out how to get an enormous digital project from my computer into a form that other people could access.
I also think this is a part of creative work that people don’t always consider. We tend to focus on the finished product. We talk about the book, the album, the film, the artwork, or the poem. We discuss the result and sometimes the process that produced it, but the less glamorous logistical work often receives much less attention. Yet getting something ready to share can require a tremendous amount of effort of its own. A manuscript has to be stored somewhere. A file has to be converted or distributed. Links have to work. Readers need a practical way to access the work. And when the project is exceptionally large, every one of those steps can become more complicated than expected. The work doesn’t magically become available to the public just because the creator has finished making it.
In my case, the logistical difficulties were part of the price of pursuing an unusual goal. I wanted to create something massive, and I knew that the tools I used would eventually have to deal with the consequences of that decision. I could have avoided some of these problems by choosing a smaller project. I could have decided that millions of words were too much trouble, that the manuscript would be too cumbersome to manage, or that the challenge wasn’t worth the hassle. But that would have defeated the point of what I wanted to do. I wasn’t trying to create an ordinary poem. I was deliberately exploring an extreme version of the idea, and I knew that going to extremes would probably involve encountering extreme inconveniences along the way.
Ultimately, I did it because I wanted to. That is the simplest explanation for this entire project, including the frustrating parts. I wanted to see how far I could take the poem, how much material I could assemble, and what would happen when I pushed the tools I was using beyond the scale of an ordinary writing project. I wanted to test the process, work around its limitations, and see what I could accomplish. I knew that things would go wrong. I knew that I would have to troubleshoot problems. I knew that the project would eventually become cumbersome. I accounted for those possibilities and continued anyway. The fact that the process wasn’t smooth sailing didn’t make me regret the goal. If anything, it became another part of the story.
And now, after all of that, I have a finished manuscript containing 7,007,317 words, 561,009 lines, 156,640 paragraphs, and 15,345 pages. Those numbers tell you how large the poem became, but they don’t tell you everything about what it took to get there. They don’t capture the failed attempts, the technical headaches, the time spent working around limitations, or the process of figuring out how to share the result. They don’t show the moments when I had to stop thinking like someone creating a poem and start thinking like someone managing an enormous digital document. They certainly don’t capture every moment when I looked at a technical obstacle and thought, in much less polite language, that this was becoming ridiculous.
But ridiculous was part of the point. I chose to undertake an enormous project, and I followed it through the creative work and the logistical mess that came with it. I tested the tools. I pushed against their limits. I learned that producing a massive manuscript and distributing a massive manuscript are two very different challenges. And despite the obstacles, I kept going until I had something I could share.
Would I recommend that everyone try to create a seven-million-word poem? Absolutely not. Most people have no reason to put themselves through this particular combination of creative ambition and technical frustration. But I am glad I pursued it, because I wanted to find out what would happen. The point was never that everything would work perfectly. The point was to attempt something enormous, deal with the obstacles that arose, and see the project through.
So yes, the infinity poem is finished, but getting it out into the world has been its own adventure. The announcement tells you what I created. This post tells you a little more about what it took to make that creation shareable. One part was about generating and assembling the material. The other was about wrestling with the practical realities of storing, converting, and distributing it. Both were part of the experience, and both deserve to be told.
I wanted to create something massive. I knew the process would test me and the tools I used. I pushed through anyway.
And now, after all the glitches, limitations, frustrations, and troubleshooting, I can finally say that I got it done.
