Category Archives: Geek

I’m a geek. I love technology, especially communications technology. So, any time I’m dealing with geeky stuff it’ll show up here. As my geekiness is linked to my pastoral call, however, this stuff will often be found elsewhere.

Training Revolution

Command KeyThe buzz was running among Geeks this week Teens are bored with FaceBook. I’ve been saying for a while that the kids who grow up in the era of persistent-connectivity are going to naturally find boundaries with these tools. They don’t want to be overwhelmed with social networks, that’s what texting is for. The growing trend among younger users on FaceBook is that it’s overwhelming, and they don’t want to be overwhelmed. So they are migrating to other services like Tumblr and Instagram (yes, I know Instagram was purchased by FaceBook. The article linked above pretty much tells you why).

As a technologist who works with pastors and a denominational region, this is the type of shift which sends people into a tizzy. There are still people out there who are just joining FaceBook thinking they’ll “be able to connect to young people” – and now the young people are flocking somewhere else. “Now we have to learn a whole new service,” the lament goes.

This lament is the problem.

Whenever I teach people technology skills, I make an effort to not focus on simply one tool. Rather, I try to teach skills which can be translated from tool to tool. These skills will often need to be tweaked depending on the tool at hand, but once the skill is embedded tool-changes cease being moments of, “I don’t know what do to!” panic. Instead, they become moments where a user is freed to think, “I know this is possible, how can I do this?”

A good example of this are hyperlinks. Early on in the web’s life, when people saw blue, underlined, text emerging users understood clicking on that text would take you somewhere else. As the years have gone on, even as the traditional look of hyperlinks has long-since ceased being popular, people still understand clicking/tapping blue, underlined, text will take you somewhere. The skill has been learned, and therefore works on web-pages, social networking apps, eReaders, and even Bible software. People don’t look at an underlined asterisk or or number in an eBook, for example, and panic. They simply know what it does.

The holds true for tools like word processors, presentation applications, spreadsheets, and web-browsers. If users learn the skills needed to use each kind of tool, it shouldn’t matter if they are suddenly set in front of an unfamiliar application. There will certainly be over-lap. Many of the formatting icons are the same across tools, after all. Where there is no overlap, however, users need to be trained to understand the functions they need to be productive, and invited to explore how they might be implemented in another tool.

This also holds true on social networking sites, which brings us back to the lament over the abandonment of Facebook by teens. The “tool of the day” will always be shifting, that is the nature of the web. So instead of fixating on learning how a particular social network works, we should be teaching people what it can do. Facebook has “friends,” people with whom users share pictures, updates, and comments. Google+ has “circles.” Twitter and Instagram have “followers.” The ideas are different, but similar.

If people are completely fixated on the fact that Facebook has “friends,” and that’s the only way they know how to connect on social networking, they when they open Google+ and see “circles” they will be lost. If a person has been taught to think, “Social networks are about making connections” then perhaps they will be freed to explore how that particular tool manages to make those connections.

This a dramatic shift in the way we train people to use computers, reliant on teaching people to develop instincts every bit as much as repetitive skills. It is, however, a perfect time to be implementing such a shift. The arrival of touch as a pervasive computer interface has opened up a whole new world of instinctive computing – more so than even the icon-driven interfaces of old. Instinct, developed through years of experience, tells us we can move objects by flicking and swiping – so we do this naturally on our phones and tablets. Instinct tells us pinching is a good motion to make things larger or smaller, and so we do this. Now that the interfaces have caught up with the way people actually function in the world, it’s time our training methods caught up as well.

Textbook pain

My son is visually impaired. It doesn’t slow him down all that much, but it does make school more difficult than it would be for him if he had better vision. Several years ago we got him an iPad so he’d be able to read – it’s been amazing for him. The iPad has become my son’s notepad, eBook reader, and word processor. The ability to pinch-zoom on just about anything really is magical (yes, geeks growled at Steve Jobs when he referred to the iPad with that description, but it is amazing). This year he’s even able to scan workbook pages with an app and import them into Notability to edit (that is, when he’s not feeling too self-conscious).

The only place the iPad hasn’t been helpful is with textbooks. School textbooks layouts take visual stimuli, inject with with crack, and vomit it on to a page. I am a visual learner (as is my son), but school textbooks break up the data so much it’s almost impossible to figure out what’s important if you’re a fully sighted person. If you have difficulty seeing, it’s a nightmare. Particularly when a reading curriculum depends on “open book” tests.

Unfortunately, textbook publishers have been slow to take up digital publishing. Even when they have jumped into these waters, it’s been done tentatively. Rather than make actual eBook versions of their textbooks, publishes have opted for web-versions which are identical to the printed page. This would be a minor annoyance which could be overcome with pinch-zoom and dragging but for one huge flaw in the implementation – the online versions of the books depend on flash. Not only does this make them inaccessible on the iPad without a third party browser like Puffin, it removes the very accessibility features which make the iPad such a valuable tool in the first place. Imagine our frustration! Imagine my son’s! Sadly, Reading has sapped the joy of reading from him.

So here is my call to textbook publishers.

Please, end your tentative wading into the digital world and jump in. Stop being enamored with your busy layouts and accept that digital screens require a different type of format – a format already set for you by the ePub standard. You may still have your images, charts, and call-outs – an ePub, after all, is basically a XML file with specific extensions. In such a format all your added charts, call-outs, and “think abouts” could just be links which could be tapped in order to access. Images could be embedded into the text itself, and tapped to access a zoom-able version. By taking up this standard, students like my son could have access to the same content a fully-sighted student has, and without a suffering from a diminished experience. If he can’t see something, he may simply enlarge the text and continue reading.

I understand publishers have a business model to protect. To this end I have no problem if you apply some kind of DRM to your textbooks, linked to an account for each student. I dislike DRM intensely, but I understand textbooks are not like other books. They are meant to be used year after year in the same class context. Students don’t own textbooks (at least, not until college), they borrow them from their school. If DRM can be a way to make sure the books get “handed in,” then I’ll grudgingly make a exception for it in this case. Just understand any system you develop will be cracked, but most people will play by the rules if you treat them well.

Just, please, make the shift to standard eBooks while I can still salvage some of my son’s educational experience.

Look Ma, No Wires!

My son dressed up

Harry Potter apparently lives at my house

I was given a wonderful present for my birthday, a first generation Canon EOS Rebel DSLR. It's my first “real” camera, and getting a DSLR for free took away the obstacle of, “How can I justify getting a camera I don't even know how to use?” Now I can learn on a great device, and if/when I out-grow it I can always move up to a newer model.

I love using the camera, the ability to do depth of field, manually focus, and set my shutter speed and f-stop make taking pictures a lot of fun. White balance is difficult, and I don't much care for the “auto” settings, but I'll learn. In fact, after owning the camera for a couple of weeks there was only one thing which bugged me.

Wires.

Ever since I got a smart phone my point and shoot had been all but retired. Aside from the convenience of the form-factor, the ability to move images off my phone without wires was super appealing – especially after Photostream debuted (even if it can be a bit confusing). With the Canon, though, I either had to pop out the memory card or plug a USB cable in order to retrieve images from the device. I didn't like this even a little bit. Even worse, the camera takes compact flash memory, which meant my MacBook's built-in SD slot was useless. I needed a card reader. How 2003!

This led me to seek a solution for my wire problem. I was familiar with eye-fi, an SD card with wifi and GPS on it – so I went searching for something similar in compact flash format. Instead, I found something I'd never seen, an SD to compact flash adapter. It didn't take me long to figure out the adapter worked with eye-fi cards, so off my went my order to Amazon. I chose to order the 8GB pro x2 card, because it came with GPS included and could also transfer Raw images wirelessly.

The card arrived today, and after some testing, I had it transferring images from the DSLR to my MacBook, Nexus 7, and iPad. It's pretty amazing to have my camera send the pictures to my devices, and I can set it up to transfer only images I mark as “protected” on the camera. Additionally, when I transfer the images to a mobile device I can have them automatically transferred to my MacBook as well (though on the iPad this doesn't make much sense given the presence of Photostream). I don't know what impact this is going to have on battery life. I know it will certainly have some, but eye-fi seems to have done a stellar job implementing power management on the card.

Configuring the card requires either a Mac or windows computer, also, the eye-fi cards needs to be inserted into the SD card reader which came in the package, without it the card cannot be set up. While this is a pain, and a non-starter for people who have gone entirely mobile, I understand the limitation. Configuring the card via an on-board interface might be too much for to ask for such a compact device. The card also requires users to set up for an account with the eye-fi service. This is used to upload images temporarily to their web-service, as well as for pairing different devices with the card. This web-service keeps photos online for seven days (it can also be disabled), where they can be shared and downloaded. Long-term storage in eye-fi's system costs $49.99 a year and includes unlimited storage – that isn't a bad deal for a cloud backup of every image taken with a camera! In addition to eye-fi's service, users may also set the card to upload images to a variety of web sharing sites – including Flickr, Facebook, and Picasa.

My one issue with the eye-fi mobile apps is the location data obtained by GPS doesn't seem to be applied to the pictures. I noticed this on the desktop manager as well, pictures would appear in the manager and it would take a bit for the location data to be applied. This is because the geotagging seems to be accomplished on eye-fi's servers, but I do hope the ability to have the geotagging data applied to the photos comes to the mobile apps soon. It is, after all, one of the reasons I purchased the more expensive card. Also, the lack if geotagging data on the photos imported to iOS makes Photostream less useful – it seems to get the location data images have to be passed through the desktop software, or downloaded from eye-fi's web-site. This is kind of a bummer. If the eye-fi app can't apply the geotagging data to my images I'd almost rather it not add them to Photostream. I could simply automatically upload my images to the Mac when I returned to it. That way all the data would be attached to my photos, and I wouldn't end up with multiple copies of the same image. I can turn on the automatic upload, but keeping eye-fi images off Photostream isn't something I've figured out yet. I could turn Photostream off completely, but it's an essential part of my iPhone workflow at this point.

Despite this hiccup, I am quite pleased with the card thus far. If you use a DSLR and have been looking for a way to avoid wires when transferring you images, this is a stellar solution.

 

Continuing with the Nexus 7

image

I’ve been using the Nexus 7 for a couple of weeks so I  want to share some thoughts on how its been going. Over all, I continue to really like the tablet. My only nag on the hardware is the layout of the volume rocker and sleep/wake button. They are placed so close together I often find myself putting the device to sleep when I want to change the volume. Read on for my other thoughts.

Media Consumer

I’ve been using the Nexus almost exclusively for media consumption the last couple of weeks and its been great. One of the issues I have with my iPad is the need to go through iTunes to add media to the device. On the Nexus the file system adding media can be done several ways.

First, the Android File Transfer App allows the Nexus to be connected to a Mac via USB. Adding files is a matter of dragging and dropping.  Second, the open filesystem on Android allows me to save any file on dropbox to the device. iOS places limits on what can or cannot be easily added to an “iDevice.” Third, using a USB to go cable allows the Nexus to act as a USB host. This allows thumb drives, and even some portable hard drives, to be connected directly to the device. The camera connection kit ads similar functionality to iOS devices, but the closed filesystem limits what types of files can be added.

The ease of adding media to the Nexus makes it an ideal consumption device.

Gaming

Android does have good games, and I’ve been enjoying some for about a week. The ability to connect a game controller only adds to the experience. Even with on-screen controls games are responsive and animations are smooth. It would be even better if I could mirror the Nexus screen to a TV.

Productivity

When I first got the Nexus I was disappointed at the productivity tools for Android. My preferred work flow is to write in markdown and have my work automatically synced to a dropbox folder. When I first got on the Google Play store the crop of markdown editors was rather slim. Most didn’t recognize the .md extension common to markdown files, had limited dropbox support, and couldn’t export HTML from the app.

I finally found a passable editor called Write. The dropbox support is clunky, files have to be imported from the dropbox app and then shared back, but it exports clean HTML and has a persistent word count.

The mobile office suites on Android are a mixed bag. I’m a Documents to Go user on iOS, but the Android version was so awful I asked for a refund. Quick Office has better file management setup, but the editor only has a page layout view. On the 7 inch Nexus screen, this makes text look far too small to be a comfortable editing environment. On spreadsheets this isn’t as much of a issue, but the word processor is really difficult to use. Quick Office also, for some inexplicable reason, doesn’t have a way to select all text. This boggles my mind.

Of all the suites I’ve used on Android so far, SoftMaker is the most powerful, but it’s Google Drive integration is currently broken. In all, I hope SoftMaker fixes it’s GoogleDrive integration – it’s a solid app.

In another productivity realm, I’m still looking for an app comparable to Notability or Notes + on Android. Nothing I’ve found even comes close. Papyrus is capable, but it’s not as easy to use add its iOS cousins.

For productivity, I continue to see the open filesystem as a mixed blessing. While I appreciate the ease through which I can add media to my Nexus, I have to say I like the sand boxing of iOS better for productivity work. Cloud integration on iOS  “just works” – in Android every app tends to use the cloud differently and the integration is usually only partially implemented.

Conclusion

The Nexus made a good first impression and continues to grow on me. The immaturity of the productivity apps show when I’m trying to get work done, but the ecosystem shows signs of maturing. I still like 4:3 better for a productivity device, but the Nexus could be the sign off things to come.

Hello 2013

The last several years as December has drawn to a close I’ve taken time to reflect on the year past. As I prepared to sit down this year and write my 2012 reflection, however, I drew a blank. Instead, I began to think about my hopes for 2013. So now I write to you my goals for 2013.

Writing

I continue to have a couple of writing projects in progress. I’d like to get these completed, and add one more project to the list.

First, I would like to finish Idea Painting and get it published in the major eBook outlets, and also have an enhanced version for the iBooks store. The bulk of the material is completed, but I’d like to add more depth to the opening section, which means I will have to do some significant research. I’m beginning to compile a list of books to read, in 2013 I will get to it!

Second, I would like to finish my novel, In the Land of the Penny Gnomes, before NaNoWriMo next Autumn. I didn’t get to write much as 2012 came to a close due to my own mental weariness, but I’m beginning to feel refreshed and I’d like to get back to it! I don’t care if it is only ever read by my friends and family, it’s just something I’ve always wanted to do.

Third, I’d like to write a new devotional study for Central Baptist to journey through in the fall. In the past I’ve written studies on evangelism, pilgrimage, hospitality, and the Holy Spirit. I’m not sure where to go next, but as I sit here the notion of “calling” is popping into my head. We shall see!

Geek Goals

I have four geek goals for 2013.

First, Central has purchased FileMaker Pro so we can create a good membership database. I have our data in, but I need to create reports and queries and layout. This will take time, and I’ll need to learn FileMaker’s scripting language to do it well. I haven’t been this excited for a project like this in a while, hopefully it turns out well!

Second, I want 2013 to be the year ABCNJ gets its video studio up and running. This will require work, funding, and much learning. It’s my hope a video studio, with several live shows along with recorded news and interviews, will help ABCNJ to strengthen its sense of kinship.

My third goal is to work with the ABCNJ staff to better equip them to use the regional tech tools. Being part-time can be frustrating, I see holes which I can’t properly address due too sheer lack of time. This year we will try to remedy that.

Finally, now that my kids are both hitting adolescence, as are their friends, I feel the time is right to work on a project I’ve pondered for years – an internet safety seminar. My wife has been incredible working with our daughter as she learns the freedom of having a phone, and it has inspired me. The lessons we’ve learned in our home, along with my technological understanding, are a valuable combination. I’ve already written a rough outline, by spring I’d like to have it put together. If this can be a skillshare class, so much the better.

Pastoral Goal

I have one main pastoral goal this year, finish our transition! Our transition team has done admirable work, it’s now time to put it to use and let the Holy Spirit use it to take us toward our next journey as a congregation.

Conclusion

These goals, along with my normal work of pastoral care (preaching, visiting, praying, teaching) and ABCNJ’s normal rhythm (Annual Session approaches), should keep me vocationally busy for 2013! As always, however, family comes first. With all my lofty goals, being a decent husband and father trumps my other goals (I have no illusions about being good at either role, I just try to do my best and not screw my family up too much in the process).

A day with the Nexus 7

image

This week I picked up a nexus 7. After spending a day with it I can say, “This is a slick device.” Let me share some of the ups and downs I’ve had in the day I’ve used it.

The good

The first thing I love about the nexus 7 is the hardware. This device just “feels right” to hold and use. The screen is brilliant, and the dimpled back makes it easy to hold. The device is inexpensive, but it doesn’t feel cheap.

There are also a lot of features I love about Android jelly bean. Task management is STELLAR, and notifications are very nice as well. The way Jelly Bean’s launcher is customizable is also wonderful. The task switching and management are, in particular, well beyond anything Apple has done.
Being able to swipe the keyboard to type is also amazing (I’m typing this post that way right now). It takes some getting used to, but the more I use it the faster I get.

Google integration is also great, if also a bit creepy. I no sooner set up my nexus 7 when I started getting chat notifications from a friend of mine. That threw me for a loop! While creepy, its also useful. My calendar immediately loaded into the application, which also puts iOS to shame, and adding dates is incredibly simple. Google+ integration is also well done, though I do think the iOS app is a bit better (update, after updating my apps, Google+ on Android is every bit as wonderful as on iOS).

I also have to give props on the battery life, I’ve been using my nexus all day and still have 17% left in the tank, that’s very good. No need to worry about needing to charge in the middle of the day.

The not so good

As good as Jelly Bean is it still isn’t as easy to use as iOS. The best way I can put it is, “When I’m using it for productivity purposes it feels more like a traditional computer than a tablet.” People have complained about Apple not opening the filesystem on iPod devices since their inception, but as I use the nexus I think they might be right to keep it off limits. The filesystem on the nexus is, for example, called, “SD Card.” I understand that means “local storage,” but a normal user might start poking for the SD card slot, or panic because they don’t have an SD card to put into the device (which doesn’t take one). It’s the type of cryptic notation I expect on a traditional computer, but not a tablet.

Also, the way files are handled, and apps are registered to handle them, seems off. Out of the box the nexus has Google play books installed, to which I added both kindle and nook readers. I then tried to open an epub from dropbox and was told I didn’t have an app able to open that type of file even though I knew I had two. It turns out that nook, Google play books, and kindle don’t want books to be loaded in by alternate methods, so they don’t register as being able to open eBook files – and there is no simple way to tell them to do so. This also hit me with markdown files which have an “.md” extension. The markdown apps I’ve discovered all save with “.txt” as their extension, and don’t register as opening the other designation. Despite the fact that markdown is plain text, Jelly Bean refuses to open the files. Now, this is as much the responsibility of the developers as anyone, but with an open filesystem it would be nice to have the option to set applications for certain extensions.

The nexus 7 also lacks miracast support, so connecting to a TV or projector is not easily done. On the plus side, I might have to pick up a raspberry pi to see if I can hack it to be a wireless display adapter for presentations, as the nexus 7 would make a great speaking device. I realize I could have gotten a kindle fire or nook hd to get video out, but I wanted the plain Android experience my first time out. I knew the device didn’t support video out when I purchased it, so it wasn’t a shock, just a bit of a bummer.

A good many people are hoping Apple makes the next iPad into a 16:9 device. After using the nexus for a day I have to say I am not one of them. For media consumption, 16:9 is amazing. For productivity, however, 4:3 simply feels less cramped.

The unhappy

A lot is said about the app ecosystems of both Android and iOS. The assumption has been that iOS apps are more plentiful, better to look at, and easier to use. I have to say I’m a bit underwhelmed by the app selection in the Google play store. My workflow for writing is to create in markdown, and have it saved to a dropbox folder where I can edit it on any other device. Currently, there is no app which will do this as far as I can tell. Some come close, but are hindered by not handling sub-directories and not recognizing the .md extension (which I find especially odd). The is also nothing quite like notability in the play store. Papyrus and lecture notes come close, but neither allows for the type of effortless writing I’m used to on my iPad. This may be because android developers tend to assume anyone writing on an Android device will have an active pen with which to write, which I don’t have. On this later point I will have to keep playing and see if I can get used to it.

The way Android handles notifications is wonderful, but it’s also a bit haunted. When I finally installed overdrive to handle epubs, for example, tapping an epub notification causes it to disappear for me, while for a friend it gives him an option to open the book. I know I must have something mis- configured, but I simply can’t find it (any advice would be welcome).

Conclusion

The nexus 7 is a beautiful device and is fun to use. At the moment I’d say it’s best suited for media consumption, rather than productivity. This is partly due to hardware limitations, the lack of miracast or video-out being key. It is also partly to the current lack of apps to support a flexible work-flow. I’m sure this will change in time, but right now work still needs to be done.

I am, however, in love with the smaller form-factor. If/when Apple comes out with a retina iPad mini, that will replace my larger iPad. For now, the nexus is a fun device that can teach Apple a thing or two. I’m glad to have it, and will continue to play with it.

Upgrades

I was thinking if upgrading my iPad in 2013. I like the retina display, and my iPad is two years old. Still, as I began to figure out what it would take to save up for a new iPad I began to think, “You know, I really like my iPad 2.” It's true, my iPad is my primary device, trumping my MacBook for just about every task I do except presentations and high-level video editing. I love my MacBook, but my iPad is like an extension of my arm.

My contemplative look

I contemplate my technological future

As I've never had a moment where I wished I had something besides my iPad 2, it seems rather dumb to upgrade it. After all, it has the same specs as the iPad mini, so it'll likely survive another ios upgrade, or even another two. So why not hold on to a device I love to use? It's not like my white MacBook, which was beginning to give me fits when creating massive presentations before I upgraded it.

When I eventually do upgrade my iPad, I'll probably go with an iPad Mini. I LOVE the form factor. In fact if the mini had a retina display and the same processor as the third generation iPad, I might have decided to upgrade anyway.

So what to do? Well, I've been intrigued by the Nexus 7 since it came out, and I've been wanting to give Android Jelly Bean a try. So I think I may be picking one up this week sometime. That, or use my wife's upgrade to get a iPhone 5 and give her my 4s.

Either way, I'm keeping my faithful sidekick. Why get rid of something that works perfectly for what I need?

 

The great migration

WriteUp iPad

WriteUp, my favorite Markdown editor, running on my iPad.

Over the past several years I’ve been on an interesting word processing journey. First, I decided to migrate from a traditional desktop suite to the online offering Google Docs (which is now part of Google Drive). I hadn’t originally expected to stick with Google Docs for my regular word processor, but I quickly became hooked on both it’s speed and the way I could integrate Google Docs with the mobile office suites on my iPhone. Suddenly, the idea of “syncing” was gone. With Google Docs my documents lived in the cloud — and my edits followed me on wherever I was.

My shift to Google Docs was significant, but even after migrating to it I was using my MacBook for my writing. Then, on a cold day in March of 2011, I picked up a device which would take me on the next step of the journey — I got an iPad 2. We had purchased a first generation iPad for my son, who is visually impaired, shortly after they came out — I was shocked by how much I enjoyed using the tablet. I borrowed his iPad several times for meetings, and was amazed by its portability, ease of use, and invisibility. I had always used my laptop when meeting with people to make plans for special services, weddings, and funerals. While the laptop was functional, it was far from elegant — I always felt like there was a wall between me and the people with whom I was meeting. When I was using my son’s iPad I kept the functionality of planning services electronically, but the wall of separation caused by a laptop vanished. The iPad had a similar form-factor to a pad of paper, and people interacted with me as though that’s what I was using. I resolved to get the next iteration for myself when it came out.

I acquired a bluetooth keyboard soon after I purchased my iPad, and decided to try my hand at writing a sermon on the device. At first, I didn’t much care for the process of writing on my iPad. The interface in my mobile office suite was clean, but it took too much effort to change formatting. It also didn’t have support for paragraph styles to create structured documents. In the end, however, the extreme portability of my iPad won me over. The iPad was lighter, less obtrusive, and lended itself to distraction-less writing. It got to the point where I actually felt annoyed when I had to use my MacBook whenever I sat down to write my sermon.

For over a year I wrote my sermons on my iPad using a mobile office suite. It worked. The suite had some good outline support, and synced with Google Docs very well. I still wanted a decent setup for paragraph styles and was irked by how hard it was to format text — but the pros of writing on my iPad outweighed these frustrations. Then two occurrences converged and changed my sermon writing work-flow one more time.

The first of these was the shift from Google Docs to Google Drive. Suddenly mobile suite, which had played well with Google Drive so well, became unstable. This was not an acceptable state of affairs, and I began to wonder if there was be a better workflow for me.

The answer came to me when I became aware of a plain-text markup system called “markdown.” The simple style-codes in Markdown keeps documents human-readable while allowing for the creation of highly structured documents, and quick exporting to PDF, HTML, and other formats. The flexibility, ease of use, and incredible portability won me over. I traded the ability to outline as I’d been used to, but gained the ability to write documents with good structure and clean formatting without having to ever take my keys off the keyboard. Now my documents live in dropbox, are synced in real-time, and have no dependency on a specific file format or service to continue being useful for years to come. Even if dropbox goes away, for example, I’ll still have my local copies and be able to read my files with any text-editor. It’s been quite a journey over these last couple of years from a desktop office suite, to cloud-based office suite, to dropbox linked plain text markup which is truly mobile.  In fact, this post was written in markdown, I just copied it’s HTML output to the WordPress editor.

While I’m not using Markdown for all my writing, I’m currently writing a novel in Scrivener, I am no longer worrying about manually formatting my text as I write.  It’s been quite freeing.

Using Paragraph Styles

It’s been quiet here for a while, but today I finally had a chance to sit down and create a quick video on using paragraph styles when writing.

Rule of communication

A picture of wezlo

I want to take a brief pause in my “styles” series to share some thought on how/when I choose to communicate. I'd love to hear your own thoughts in the comments! I'm calling this a “rule,” in that it helps to order my electronic communication life.

Phone Calls

I am well-known for my general aversion to voice calls. I feel as though I am intruding on another's time. Probably because I find them intrusive myself. I have several friends I will talk with at length on the phone, but for “just sharing a line of data” moments phone calls get in the way.

Having said that, I have many people with whom I minister who use the phone their method of choice, and I accede to their style in order to stay in touch – but I have a rule for doing so.

  • Unless it is an emergency I never call a number before 10 AM, and never after 8 PM. People need time to be by themselves. Most people I call at a home number are seniors, and I find those hours work best for them.
  • When calling a cell phone, I try to be aware of when people might be on the road.
  • I never call any number between 5:30 an 7:00 because I want people to be able to enjoy a meal without interruption.

Texting

Texting is interesting because it is not as intrusive as a voice call, but also implies a sense of immediacy. I try to keep both these aspect in mind when communicating this way.

  • I don't text before 9 AM unless I'm set to meet someone and I'm letting them know my location. Before this time people are often settling in to work or preparing for the day, so I let them do so.
  • I don't text after 9 PM unless it's a “shared” experience. I'll text about a Phillies game with a friend, or about a show I know someone else is watching. I won't just text, “Hey, what's up?”

Instant Message

Instant Messaging is still a way I enjoy communicating. The rule is simple.

  • If someone's status is green, I can strike up a conversation regardless of time. If the person responds or doesn't respond is entirely up to them.
  • I'm someone's status is yellow, which means idle, I have no problem leaving a message.
  • If the person's status is red, I won't start a conversation unless they have an away status which show they are not occupied with work. An “in a meeting” means I won't strike up a conversation in any circumstance. If the status is, “I'm at lunch” have no problem leaving a message. If there is no specific status given, I don't send a message.

Social Networks

Social networks are simple.

  • Anything but instant messaging is “anything, any time.”
  • Instant messaging is something I will only initiate with a friend I actually know, and then keep the conversations brief.

Email

Email is the most simple of all.

  • Unless I know the person is on vacation, I'll write a message any time.