Hey! You may be wondering, "Did SXSW swallow Mike whole?" I'm back today to say no way. The last two days have been a blur of tech, meetups, and parties. I am utilizing my time way more than last year and because of that I haven't had the to report all of the action. So, bear with me as I try to run down what's happened. Let's start with Saturday all quick fire style:

The first panel talked about 'Tools and Processes for ADD Project Managers/Entrepreneurs.' Essentially what this panel talked about was methods that one can use to help fight any external or internal items. There ended up being two people, one a marketer tech type and another, who was a therapist. Their whole gist was that we need to have hto counteract the different types of issues facing ADD type people. It wasn't anything I was not used to. Some of the methods included using lists and to do lists, which I do already with the GTD methodology. That said, it was a nice refresher that pointed me to other methods to fight distractibility beast.

Next up was a whole set of Future 15 talks revolving around the government. My day job includes work in the government contract industry so these sets of talks helped me out to determine what more I can do as well as what ways my company to become thought leaders in. The gist of all of the talks revolved around 3 items:

• Open data from the government is ripe for the picking
• There's still a need to make things super simple for all citizens
• The government retires more than half of their workforce and it's time for young tech-type people to take their place

I have to say, no matter my or your political preference that there is ripe opportunity to take advantage of what everyone is saying is a slow, hulking beast. That's right, the government. Not only will there be funding available, but there's also innovation for taking some draconian methods and turning it into something more 21st Century.

The final talk was a workshop for yours truly. The workshop titled 'Building Native Apps Across Platforms' dealt with the delimma of supporting one application across many mobile devices. I saw Jonathan Stark's talk last year and was happy to see him again with the guy from Sencha Touch and Appcelerator Titanium. What I got from this talk was a couple of cool CSS3 type methods and a great run-down of Sencha Touch. I didn't know that you could do more than just include a library of mobile friendly frameworks. You can do MVC as well as more proprietary framework items. It's a good thing it's a free license.

Once again, I took to the night in all of its glory. Saturday night saw me and my lady head to the Frog Design Interactive Opening party. Just like last year they had some cool human interactive toys to play with. The favorite for me was the Angry Birds rip off called "Hungry Birds." You had to jump a certain way on the stage to have your bird chomp. The other thing that was pretty cool was the Ableton Live like controller for humans that involved people actually standing on squares to activate signals to the layer. All in all it was pretty cool. I think we went to other parties but that's all I remember now. I'm sure pics and recounts will follow soon.

A couple of different developments cropped up in the last couple of months that's pulled me away from the blog.  One of them was a job change.  The company I'm working on a contract to hire basis is great and I've had the opportunity to learn many things in my short time there.  I do PHP programming and I had the opportunity to freshen up on PHPDoc.  PHPDoc is a documentation standard much like JavaDoc where you can comment code and drop in identifiers to help with the status of a certain function or class.  One of the identifiers is '@todo.'  After working with the history of the '@' symbol and how it relates in context, especially with GTD,  I came to realize how much this 5 character identifier has affected my life.

The '@todo' identifier states one thing clearly:  The following information is what's left or what's next to do.  It can be compared to the @NextAction context in GTD.  Once that action is completed, there may be another one next and subsequently a '@todo' identifier with that information will be listed.  The difference between that and GTD is that it's left in the code.  But, with a good IDE or a simple awk command, you can compile the list of @todo's for a project thus returning it to a GTD like state.

I'm the kind of person who's insane attention to detail will leave me always uncovering a rock or looking at a problem from all perspectives.  Some people call this being a pefectionist.  One of the major problems with being a perefectionist is that they will refine and tweak themselves into never getting anything done.  Analysis through paralysis is a common phrase for the problem.   And yes, I have that problem.

As some of you may know, a couple of years ago I hit rock bottom in paralysis and have somehow climbed my way step by step by implementing the GTD mehtod (as well as making other life changes).  The perfectionist in me still lives.  The initial mind dump and inbox organization took me about 3 days.  One of the hardest things to do while implementing the methodology was not being sure I was doing it right.  The common voice of the perfectionist.

So I'm slowly learning ot become an almost-perfectionist.  I still do my tweaks and twinges, but set a time limit before sending the product off.  Whenever I do so, there's that voice that doubts whether or not I've done right.  Even when I use a time limit, it reaches out and pulls me down to make sure I double check and triple check everything.  It's going to be with me forever.

Last month, an 'ah-ha' moment came.  And no I'm not talking about jumping up and singing 'Take on Me.'   What I'm talking about is when I started brushing up on PHPDoc, I realized that the '@todo' was the trademark for the perfectionist.  I can roll some code out but appease the perefectionist in me with the simple 5 letter incantonation.  The code is out and I can always come back to it to tweak and twinge.

I've accepted the fact that I will never be happy with my work.  I've also accepted that I will always find something wrong with it and attempt to fix it on the spot.  But with the '@todo' action I can drop the noted fix and move on.  I feel much more relieved and am producing more now that I've left @todo's not only in my code, but also in my other projects, my friends, my family, and my life.

While I was going through the twitter round up, I couldn't help but notice that the semantics used to address other tweeps include the @ symbol.  That got me thinking about how the @ symbol shows up not only on some web services, but also email, blog comments, and even in the Getting Things Done methodology.  I also recalled someone saying that the German name translated to "monkey tail" instead of the widely used "commercial at."  After some research, I discovered where the ubiquitous nature of the @ symbol symbol fits and where it potentially could grow.

To get a good handle on the @ symbol, we need to look back and see where it came from.  Not much is known of the exact time it showed up, but different theories all point to the @ symbol used to represent something more efficiently.  An Italian merchant used it to give it a name for a certain quantity of jar stuff.  Another story is that monks used it to combine the word at to one letter.  How verifiable each origin is seem irrelevant.  The point is that the @ symbol makes things more efficient.

The @ key showed up on the typewriter then IBM keyboard.  It's called commercial at because of what accounting institutions use it for.  It's in the ASCII set.  What's even crazier are the names.  A monkey tail and elephant trunk and the like.  Some countries call it another animal.    There's always some lore for the @ symbol.  There is a special meaning between languages.

The @ symbol took on another meaning in 1972 when Ray Tomlinson used it for the very first email address.  He was looking for something to point a message to a machine.  Since the @ symbol literally meant at or commercial at, it seemed like a logical placement.  So he fired up some code and thus began the use of the @ symbol in electronic communications.

Today we see the @ symbol used in a couple of different communication contexts.  We of course use it for the email address.  But now we can use it for comment replies in message boards.  We can use it when we designate a user on a machine.  In some other cases, it can be used to address others individually in email messages to groups.  More importantly we can see its use blowing up on Twitter.

When I mentioned contexts, it opened the door to the @ symbol's use in the Getting Things Done methodology.  David Allen created GTD as a task management/productivity system.  Part of what he preaches is the use of a Next Action list.  With each list you can group actions to locations and other objects.  The system is agile enough to account for multiple lists of actions designated by a noun.  He suggests the @ symbol for these special lists while organizing so it can show up first in the folder listing on a computer.

The great thing is the suggestion also helps marry the @ symbol with the context with which it precedes. Now you can have lists for @Home or @Office or @Phone if you need to call somebody.  While originally it was a listing workaround, now the @ symbol has more an integral role for context definitions on GTD.

We are beginning to see patterns develop at how the @ symbol is taking on a powerful role in communication.  We are seeing the @ symbol used to tie context not only to locations, but also to people.  Where in GTD you have a location, now with Twitter or email addresses you have a person.  The use of the @ symbol is becoming a gray area of distinction between a person and a place.  The  word after the @ symbol is the noun.

Now you can see where the action or verb takes place.  In GTD you have an action to do at a place or context, now you can send a message or 'tweet' to a person.  When you're responding to someone else that drops a comment in a blog post, you are responding @ the user.   When you see a tweet pop up and you are compelled to respond, you type out @ and the user name to respond to their post.  What does this mean?

This paradigm shift of acting on a noun shows the idea of a context is more prevalent than ever.  The lines have blurred between machines and people.  There is a singular unifying context for people now.  Because of that, there is more consistent applications across different media and communication.  What this roots down to is better organization for social organization.  I can email guy@aplace.com or just twitter @guyplace or note in my system to call @gplace in my @Communication list.

The more use that comes from it, the more common it will be.  Even Twitter founder and CEO Ev Williams talked about how the @user response wasn't in the design of Twitter to begin with but that it naturally bubbled up from the community use.  The paradigm naturally evolves to what we are most comfortable using.  In Twitter Ev saw that and responded by giving it more meaning within the Twitter ecosystem.

Where can this take us in the future?  Perhaps there will be a time where a service will be attached to a user on the domain.  So if you email me at mike@hoketronics.net, you may actually send it as email@mike.hochanadel@hoketronics.net.   Or if I'm not there it could be forwarded to twitter@mike.hochanadel@hoketronics.net, or phone@ or facebook@ or myspace@ and so on and so forth.

My initial thoughts lead me to what the open ID folks are doing (save that for another research post), but I'm not sure if they've incorporated this simple,  powerful, and  NATURAL paradigm of using to the @ symbol to address nouns.  Hopefully they will.  But what we can see is that the use of the @ symbol to address nouns will grow stronger and will almost become subconscious.  What great leaps and bounds we have come from a silly little monkey tail.

Needless to say, the holidays brought me some changes this year on both the personal and professional side.  A couple of years ago I implemented the Getting Things Done (GTD) methodology to help account for changes in my life and to influence the direction it was going.  I recently had the opportunity to start a fresh GTD setup at the office.  Here are the steps:

1. Download Thunderbird 3 Beta 1



2. Setup the mail account.  Mine was an IMAP implementation so access to it via a webmail interface was kept in place.



3. Download and install Lightning Daily Updater.  The current stable version is for Thunderbird version 2.  This Add On for Thunderbird grabs the nightly, version 3 compatible calendar extension.
4. Be sure to enable the Google Calendar Provider in the options for the updater.  This was used to sync up office specific events to my main Google Calendar.



5. Run the updater and install both Lightning and the GCal provider



6. Add 3 local calendars for the main GTD contexts: @NextActions, @SomedayMaybe, @WaitingFor
7. Setup main calendar to sync with external Google calendar, using the private XML url from your calendar's settings.



8. Setup the projects context as Categories in the Lightning Preferences

This is a little bit different than what I had before.  I'm taking the calendar/task approach much differently.  Before I used Horde's implementation of their organizational modules to manage an action and an action that was time sensitive.  With Thunderbird and Lightning, the idea of a task is strongly coupled with a calendar item.  So I had to create the separate local calendars to give a place for tasks to land.  This turns out great because now I can create new contexts in the future as separate calendar types.

So far the implementation is going well.  I more times than not funnel all tasks Thunderbird's way but have caught myself once or twice avoiding the email client.  The next step for me is to explore what the benefit for me in syncrhonizing this setup with my Gmail/RememeberTheMilk system for my main GTD implementation.  It's still a little early, but if I feel the need to jump ship, I'll let you know.

Update 6/5/09: Changed the download link for Thunderbid beta.