From Post-it Notes to “Fuck It, I'm Building a Database”
From Post-it Notes to “Fuck It, I'm Building a Database”
It started with a few Post-it notes.
Nothing particularly complicated. Just the occasional detail I didn't want to forget. A character's name. Something about their history. An idea that occurred to me while working on something else.
Perfectly reasonable, really. People have been using Post-it notes to remember things for decades. They're cheap, convenient, and don't require a software licence.
What could possibly go wrong?
Well, apparently quite a lot.
The Notebook
The first problem with Post-it notes is that they're exceptionally good at multiplying.
One becomes five. Five becomes twenty. Before long, the supposedly convenient little reminders have become a collection of disconnected thoughts with no particularly sensible way of finding anything.
So I bought a notebook.
An actual notebook, with pages. Revolutionary stuff.
Everything could go in one place. Character information, ideas, notes about the world, things I needed to remember for later. It seemed like a perfectly sensible solution, and for a while it probably was.
Until one notebook became three.
I'm not entirely sure when that happened. Presumably there was a perfectly reasonable justification at the time. There usually is.
The difficulty with three notebooks, of course, is that you now have three different places to look for something you could previously find in one.
Assuming you could find it in the first place.
Surely a Spreadsheet Will Fix This
Clearly, the problem was organisational. Paper had served humanity admirably for centuries, but it was time to embrace technology.
At some point, I decided a spreadsheet was the answer.
Now, before anybody laughs, spreadsheets are extraordinarily useful. You can organise information into columns, sort it, filter it, and generally impose a degree of structure on things that have previously been behaving like an unruly collection of sticky paper.
Characters in one sheet. Locations in another. Perhaps timelines, relationships, and other bits of information arranged in ways that would make everything wonderfully easy to manage.
Except there's an awkward little problem with trying to represent an increasingly complex fictional universe in a spreadsheet.
The information doesn't always fit neatly into rows and columns.
One character can have multiple relationships. A location can appear in several books. An event can affect characters who aren't even present when it happens. And changing one detail can have consequences that extend considerably beyond the cell you've just edited.
Suddenly, you're not asking where to store a piece of information.
You're asking how different pieces of information relate to one another.
Enter Obsidian
Clearly, the problem was still organisational. Spreadsheets had served me admirably, but it was time to try something that could handle the connections between all these disparate pieces of information.
Obsidian seemed like a good solution.
Digital notes. Searchable information. Links between related subjects. A way to connect characters, locations, events, and ideas without having to remember which bloody notebook contained the original information.
That was the attraction, anyway.
And to be fair, Obsidian is a capable piece of software. The problem wasn't necessarily the tool. It was what I was expecting the tool to manage.
A Veil Sundered wasn't just a collection of independent facts. Characters had relationships with other characters. Those relationships changed over time. Events occurred in particular places on particular dates. Information revealed in one book needed to remain consistent with something that might not appear until several books later.
I wasn't merely recording notes anymore.
I was trying to maintain an interconnected fictional universe.
And that's when the engineer in me started getting ideas.
Fuck It. I'm Building a Database.
I can only imagine how inevitable this must appear from the outside.
A man sets out to write a series of novels and somehow finds himself contemplating database architecture because the fictional people he's invented have become too complicated to manage using ordinary stationery.
But once I'd reached that point, it actually made sense.
A database could provide a central place for characters, locations, relationships, events, and the other details that make up the world. More importantly, it could preserve the connections between them.
Rather than trying to remember whether I'd recorded something in a notebook, a digital note, or a spreadsheet, I could begin treating the information as part of a structured whole.
Of course, building a database introduces its own collection of problems. Because apparently what I needed while writing a series of novels was another software-development project.
Still, there's something rather satisfying about being able to organise a complicated fictional universe in a way that makes sense.
Even if getting there was a little ridiculous.
All This Just to Write a Book?
That's probably the funniest part.
None of this was the original plan. I didn't sit down one morning and decide that what my writing career needed was a custom information-management system.
I wanted to remember a few things about my characters.
That was it.
And somewhere between a Post-it note and a relational database, the whole enterprise acquired a life of its own.
The books are still the point, of course. The technology exists to support the stories, not replace the process of writing them.
But if there's one thing I've learned from this particular exercise, it's that I'm apparently incapable of leaving a perfectly good organisational problem alone.
All I needed was somewhere to put a few notes.
Fuck it. I'll build a database.
Naturally.