Archive for the 'Writing/Literature' category

 | February 1, 2012 11:06 pm

In this series, we’ve covered a lot of ground. We’ve looked at the basics of Subversion and talked about why you might want to use it for a writing project. We examined some of the advanced features, and how to dive into the history of your work. Then, we detailed how Subversion can be used for collaboration: the way locks help writers to own their ideas, how the log facilitates communication, and the way in which branches help to prepare drafts for review.

There is really only one thing left to talk about: conflicts, errors, and their resolution.

Show me more… »

 | January 30, 2012 2:30 pm

When I started talking about the ways which SVN can enable collaboration, my goal was to show how you can replicate some of the best features of a paper based workflow and then supplement them with the power of digital tools. We’ve already looked at some techniques for doing this, using file locks to promote idea ownership and leveraging the SVN log for communications. In this article, we’ll take a look at one more feature that makes it easier to work with others: using SVN snapshots (or branches) to facilitate the review of your work.

Here, I want to reiterate one important point: creating drafts that can be consumed by others is extremely important. It forces you as an author to find break points where you can send something definitive. Finding these points, where you can draw a line in the sand and say “draft …”,  causes you to solidify your thinking and take an important step toward completion. You may end up throwing the whole thing away because it was ineffectual, but that doesn’t mean the exercise was futile. The process of creating something, a draft, is an enormous step toward completion.  You’ll likely take many such steps, but each one results in a better manuscript.

SVN branches can be a huge help in drawing your lines in the sand.

Show me more… »

 | January 27, 2012 2:30 pm

After reading the previous article, you may have the impression that I think collaborative writing is a bad thing. Nothing, however, could be further from the truth. When you write with others:

  • it’s possible to distribute tasks according to individual strengths, meaning that the finished product will (probably) be more than a sum of the parts
  • brainstorming is more effective, more people means more ideas
  • not only will you have more ideas, but as you discuss, challenge, and research the topic amongst the group, you will have different ideas than you might develop on your own
  • having many people working on a project gives it energy and focus, which is tremendously helpful upon entering the hinterland of any project commonly known as “middle”

Collaboration is good, but it is also complicated. It takes a great deal of work for a collaborative project to be success. You have to balance competing needs against one another. On the one hand, it is really important to provide an author the freedom and space required to own her ideas. At the same time, though, you need to make sure that everyone is clearly communicating about the project and where it is headed.

Making sure that everyone is on the same page and that efforts are coordinated is a complex challenge. It requires meaningful discussion happens; establishing a system for sharing documents and knowledge; and that goals, scope, audience, and purpose of the project are well defined. In many ways it shares much in common with another complex endeavor, coordinating the care of a medical patient.

Show me more… »

 | January 25, 2012 8:21 pm

Though they are wonderful tools that have transformed how we live and work, computers also cause about as many problems as they solve. We can see these problems in the way that work has crept into our private time via email; in the ways teenagers choose to socialize with their peers via text messaging and social networks, often to the exclusion of the world around them (and parents); and in the way that we prepare the written drafts of our work.

In each case, these problems aren’t the result of malicious intent. Rather, they were unforeseen consequences of a transformative technology. When it was originally developed, email was a great way to quickly exchange letters with friends and colleagues. Its original designers never intended it to become the way in which a large number of people organize their daily lives. Nor was the introduction of text messaging or social networks meant to cause teenagers (or adults) to socially withdraw into an online world, but to provide an efficient and convenient way to keep people connected. This is also true in the changes that word processors and communications software have brought to the process of writing.

Show me more… »

 | January 24, 2012 7:00 pm

If you’ve read parts one and two of this series, you should now have a pretty good understanding as to what version control is and how it can benefit you. You’ve seen how it can be used to keep a backup of your files, synchronize your work between computers, and ensure that you will never suffer the panic of losing your work.

But that’s really only the beginning. Hopefully, you’ve taken things to the next level and feel comfortable digging into the revision history to look at past drafts, make comparisons between documents, or to see how your work has evolved.

Mastering the basics of version control, followed by the finer points, is a fantastic way to be more productive as a writer. By relegating the job of backup and synchronization to a tool, you can spend more time actually writing (and who doesn’t want that). Having the ability to look at how you’re writing has evolved can make you more thoughtful. Both are powerful additions to the scrivener’s arsenal. If you can believe, it though, there is yet another level which allows Subversion to be even more helpful: using it to work collaboratively.

Show me more… »

 | January 20, 2012 4:30 pm

In the last article in this series, we looked at a few of the features that version control (specifically Subversion) offers to a writer, coder, or editor. These benefits include the ability to track all of the changes made to a file in a project, synchronize your work between different computers, and automatically ensure that everything is backed up. But though these are invaluable contributions to a writer’s workflow, they only scratch the surface of what Subversion is capable of doing.

In the next few posts, I would like to dive a bit deeper and take a look at a few of Subversion’s more advanced features, such as:

  • How to compare newer changes to older versions of a file
  • How to use Subversion’s collaboration features to work with others
  • How you can resolve errors that might arise from incompatible changes made to the same file

Though Subversion’s basic features are tremendously powerful, it’s the advanced options that make it indispensible. You know, the little things that live in the background most of the time, except when you really need them. This rest of this series is about how to leverage those. The first of those features we will look at is the revision history.

Show me more… »

 | September 26, 2011 8:48 pm

Erick-Larson-DevilFor the past several months, I’ve been reading Erik Larson’s wonderful book, “The Devil in the White City,” which tells the story of the Chicago 1893 World’s Fair. (More properly called the World’s Columbian Exposition.) It’s been a marvelous experience.

Actually, that doesn’t go quite far enough in its praise. Devil is a magical book in almost every way that matters. It’s the sort of thing that (if you’re not careful) can swallow you up and send you into other worlds.

Indeed, that’s one of the reasons that I’ve spent so long reading it (eight months and counting). Larson keeps enchanting me down some of the 19th century’s most scenic, semi-forgotten by-ways. It can take some time to come back.

For example, I’ve learned about the sordid history of the Whitechapel Club, the polite hazing of women architects (with attendant nervous breakdowns) by prim society women, and a failed expedition to retrieve a tribe of Pygmies for public exhibition.

While these side stories only tangentially touch on Larson’s main narrative, the building of a world’s fair, they make the book. They help to flesh out the world and time in which the  Exposition took place and to place its events in context.

Show me more… »

 | June 9, 2011 5:51 pm

At the moment, I’m entranced with eBooks. There are many reasons for this (and I’m preparing a rather long blog post which explores them), but one rises above all the others: electronic books offer an author the best way to tell complex stories.

If you don’t believe me, take a look at this video from TED, which demonstrates a “next generation electronic book” called Our Choice, by Al Gore. (The video is only four minutes long and well worth your time.)

Though I may be succumbing to hyperbole, I really think that we are seeing the future of non-fiction. We live in a tremendously complex world and those of us who in the business of shaping and communicating ideas — scientists, engineers, idealists, philosophers, teachers, and so forth– face an enormous challenge: how do we take that complexity and make it understandable to others?

For centuries, books have done an excellent job of combining two types of media: text/narrative and images. But while you can communicate many ideas with text and images, there is still a limit. For example, who really thinks that math and certain scientific disciplines are best learned by reading a book? Even an excellent mathematical textbook is only an adequate tool, hardly an exceptional one. It simply leaves out too much of the logic necessary to understand how certain relationships are derived. In such cases, one of the best ways to understand those relationships is to watch them be derived in front of you. When done well, think Richard Feynman, it’s much more instructive than a text narrative could hope to be.

This is where electronic books might take up the slack. In addition to text and images, it’s possible to add video and even interactive elements. There are certain principles that are best explained by a narrative and video clip. There are other concepts where an interactive examples best illustrate an idea. And there are still others where trial, error, and feedback are the best way to teach the concept. With an electronic book, you can include all three. Indeed, just about anything you can do on the web is possible, which is really exciting!

For the electronic version of the Open Source Writing book, I’ve been experimenting with video. (Both ipad and the Nook Color provide rudimentary support for the HTML5 <video> tag.) In the process, I’ve learned an important point: motion and voice make it really easy to show certain points. For example, if talking about how to accomplish a certain task with a computer program, there is nothing more effective than showing how it is done. The rest of the text becomes supporting documentation.

And I think that’s cool because it expands the types of stories I can tell (and isn’t that generally the point of new technology). Cool tech without soul is just flash in the pan.

Which leads to the next important question: how do you create these amazing pieces of electronic art without breaking your wallet or mortgaging your soul? Turns out, the answer isn’t nearly so complex as you might think.

 | April 11, 2011 6:55 pm

Note: Still working desperately hard to finish the book. It is nearly done, mostly just tying up loose ends (like getting permission to use all of the pretty pictures). With that said, I’m not going to taunt anyone (especially me) with dates or tentative delivery schedules. It will be done when it’s done. The only thing I’m going to say on the timing is that it will be soon.

I had the strangest experience the other day, and for that reason, I’ve decided to write a strange essay. Here’s what happened.

I was talking with a friend (let’s call him Sam) about recent trends in technology. In the course of the conversation, we found ourselves discussing the finer points of American history. (It then devolved into the anthropology of mushrooms, but, the train of logic made perfect sense at the time. Really.)

Most of the conversation was wonderful. We cracked jokes, exchanged similar views, and generally agreed about everything. I did my usual Steve Jobs shtick, talked up open technologies, and generally babbled about my favorite things. It was a highly enjoyable exchange. Well … right up till we started talking about history, that is. That was when the strangeness happened. As soon as I said, “history,” we found ourselves in disagreement.

Not hostile disagreement or murder your neighbor contention. But it was definitely uncomfortable, and we found ourselves indisputably at odds. No one had said anything of consequence, yet, we were both prepared for a fight over a topic as mundane as “history.” In fact, now that I think on it, the whole thing was really quite distressing.

Not just a little distressing, but the crawl “under your skin and keep you up late at night” type of distressing. And all of this from a single, slightly belligerent comment (made by Sam, of course):

I hate history. Why should I care about things that happened thousands of years ago? I’m too busy trying to live in the present.

At first glance, this might seem a strange thing to get bothered about. After all, what Sam thinks about history has no effect on my life or how I live. It doesn’t impact the type of people I choose as friends or the activities I pursue in my spare time. For that matter, it’s powerless to effect the way I see or interact with the world.

On another level, though, it’s deeply irksome. This is because history is awesome, of course. But it’s also more than that. History isn’t just awesome, it’s also central to nearly everything we do. The way you understand the stories of the past influence how you interpret the future, your politics, and even how you name your children.1

This is why I had such a reaction to Sam’s comment. It denotes a willingness to disengage from the past in favor of a present without context. It also puts you at odds with reality, all 13.7 billion years of it.

image

That’s really dangerous. It leaves you adrift in a complex and stormy world without the benefit of maps, charts, or even horizon to guide you. When history is left behind, it means that you leave everything behind: science, mathematics, literature, anthropology, psychology, medicine … the whole lot. A willful ignorance of the past is also an ignorance of its many gifts. I can’t imagine hating history, it would be like hating … everything.

After I explained this idea, Sam seemed to get it. (At least he said he did. That might have just been to get me to shut up, though.) But Sam couldn’t quite let it be, he had to explain the rationale behind his comment. This is what he said:

When I said I hate history, I wasn’t referring about the sum of human experience. Rather, I was talking about the very narrow way that history is presented in schools. I hate history as a table of dates, irrelevant names, and uninteresting successions of kings.

At which point, I said, “Oh. Yeah, I hate that too.”

Which raises an important point. Why is that we teach something so vitally important to our children in such a bland form? It’s not how history is studied by the “professionals” nor is it representative of how most think about reality. Yet, it’s what we force feed our children.

Neither one of us could come up with a good answer to that question.

Luckily, it seems like the status quo might be set to change. Over the weekend, I came across the following video by David Christian (and the related project of the same name). From the video and available course materials, it looks like they aim to do something audacious: place the subject of “history” within its proper context, as the story of universal existence.

As far as I’m concerned, that is a good thing. Perhaps it might even result in a little less hate for history.

1 As a case of how history can impact child names, consider the case of Chastity. (A story which I heard over the weekend.) She was given the name by her parents, after a great aunt, in the hopes that it would inspire her to a life of service and devotion. There was even some talk of Chastity taking religious vows. None of that happened, of course, because Chastity ran away with an older man to have a family.

 | March 31, 2011 7:50 pm

In the Open Source Writing book, I’ve got a section on Visual Thinking. While I’m hardly an expert, the way we perceive and understand the world is a serious interest of mine an I read everything I can find on the subject.

This morning, while I was fact checking a few things for the book, I came across this video by Tom Wujek. In it, he talks about the neuroscience of understanding and a few of the ways that the brain interacts with the world of ideas. Though a bit dated (from the 2009 TED conference), it’s still excellent.

Of related interest, you may want to take a look at the TED project he references, TED Big Viz.