Now that TechRaising is over, I’ve been asked about four million times just what happened and what I was doing. It seems like every time I try to explain exactly what happened this weekend, I end up telling a slightly different version of the story. The weekend was so full of action and emotion that it would be hard to tell the whole thing, and I’m always focusing on different parts of it and re-thinking them.
The Back Story
Back in December when I did my first grad school residency, I came up with the idea of writing a non-linear novel. In the strictest sense, any literature that involves more than one character is non-linear because every author talks about what this group of characters is doing, and then backs up in time to fill in what other characters were doing at the same time. As readers, we understand how this works and are able to follow along. We live our own lives that way, doing our own thing all day, then getting together with our friends or family and getting filled in on what they were doing when we weren’t around.
When I talked to my husband about it, he offered to figure out the programming necessary to make it happen, but I turned him down. My husband is a genius of a software engineer, but IOS programming (I had my heart set on an iPad app) isn’t his power alley, and it would take him a while to get up to speed. In the meantime, he just started a new job and he’s still working hard at being a competitive bagpiper. Those were some of the reasons I gave him for letting him off the hook, but the real reason is that I’ve been a project manager for a long time, and my way of getting things done is to be demanding and unreasonable (although in the nicest possible way). These are great when you’re cracking the whip over guys who would otherwise spend all day sending each other links to xkcd cartoons, but less great when you’re working with someone that you have to sit across the dinner table from.