If it wasn't apparent from my pathetic cry for help the other day, even I -- one of your more theoretically productive persons in North America -- struggle with what to call things.

Tags, files, and -- dear Lord -- the innumerable assets associated with making web sites, graphics, audio, and video projects; it's all a hopeless jumble unless you have some kind of mature system in place for what you call your stuff and its various iterations. Of course, if you're like me -- and I hope that you are not -- you still have lots of things on your desktop with names like "thing-2 finalFinal! v3 (with new changes) 05b.psd".

For prior art, I still treasure this Jurassic thread on What Do I Know where people share their thoughts on this age-old problem, but, frankly I haven't seen many good resources out there on best practices for naming.

Anyhow, during a recent MacBreak shoot, I noticed that Alex and his team seem to have a pretty fly system for naming the video files that eventually get turned into their big-time IPTV shows. Thus, I turned to Pixel Corps' Research Division Lead, Ben Durbin (co-star of Phone Guy #5) for insight and sane help. And, brother, did he ever give it to me (see below the cut for Ben's detailed awesomeness).

But, just so I don't lose you, do give me your best tips in comments: What are your favorite current conventions for naming files? How does your team show iterations and versions? Do you rely more on Folder organization than file names in your work? How have Spotlight, Quicksilver, and the like changed the way you think about this stuff?

Productive Talk #04: Teams

43 Folders and The David Allen Company present the fourth in a series of conversations that David and Merlin recently had about Getting Things Done.

In this episode, David and Merlin talk about the role of GTD in teams and how to lead by example.

(Running time: 08:46)

Grab the MP3, learn more at Odeo.com, or just listen from here:

Odeo: Ian Shoales on Wasting Time

43 Folders welcomes guest commentator Ian Shoales on the subject of wasting time. (2:20)

More on Ian Shoales at http://www.ianshoales.com/

Grab the MP3, learn more at Odeo.com, or just listen from here:

Business Networking Advice: Merlin Mann from 43Folders.com - Interview

Josh asked me two interview questions about business networking, and I answered them. [Spoiler: historically, I've not been such a big fan of business networking]:

The New Atlantis - Shop Class as Soulcraft - Matthew B. Crawford

Fans of my Richard Scarry Book of the Future podcast would do well to hear a contrasting viewpoint put forth in this long essay by Matthew Crawford.

As someone who can scarcely construct a ham sandwich without requiring a trip to the ER, I enjoyed learning the perspective of a smart person whose cognitive and physical skills seem equally well-developed. I found parts to be a bit over the top in their first-world zest for manual labor -- a good friend of mine was fond of saying "You can't choose to join the proletariat" -- but you have to like Crawford's well-articulated enthusiasm for seeing mind and hand equally engaged:

Review by Fraser Speirs

Time Management
for System Administrators
by Thomas A.Limoncelli

At the end of 2004, Merlin blogged about possible extensions or specialisations of Getting Things Done for specific constituencies, such as programmers, students or parents. Thomas A. Limoncelli’s book Time Management for System Administrators is perhaps the first example I’ve seen of a book which advocates a GTD-style workflow with some modifications specific to the system administration “lifestyle”.

Book Structure

The book is laid out under the following thirteen chapter titles:

1. Time Management Principles
2. Focus Versus Interruptions
3. Routines
4. The Cycle System
5. The Cycle System: To Do Lists and Schedules
6. The Cycle System: Calendar Management
7. The Cycle System: Life Goals
8. Prioritisation
9. Stress Management
10. Email Management
11. Eliminating Time Wasters
12. Documentation
13. Automation

The core chapters for GTDers to think about are really chapters 4 through 8 and 13. The material about maintaining focus, handling email and managing stress will be familiar to regular readers of 43 Folders.

Although Time Management for System Administrators is not a simple modifier on GTD, in the sense that the author doesn’t explicitly reference GTD until the epilogue, much of the structure of Limoncelli’s suggested workflow will be recognisable to those familiar with David Allen’s book. Although Limoncelli doesn’t refer to GTD in the body of his work, it’s hard to avoid certain very obvious parallels such as the analogy of one’s memory as “RAM” (c.f. Allen’s “psychic RAM”) and the strategy of “Delegate, Record or Do” (which sounds much like Allen’s “Do, Defer or Delegate” in another order).

However, it would be unfair to dismiss Time Management for System Administrators as a GTD knockoff. It’s certainly not. One area in which I have personally found GTD to be weak is that of helping me decide ‘what to do next’. Certainly, David Allen does have some advice on that matter, but I always found it a little difficult to relate to my workplace. Limoncelli’s Cycle System is, I believe, a very strong contribution to filling that gap in GTD.

10 tips for keeping your desk clean and tidy

I linked to this very swell Life Clever article via del.icio.us the other day, but there's so much savory goodness in here, I feel like revisiting it.

Like a lot of good stuff, this article is about more than it first seems, since a tidy desk can be a MacGuffin; this is ultimately about a tidy approach, or, if you prefer, a tidy mind.

It means that you can create a physical workspace that supports your style of thinking and your approach to action, rather than having it be a purely aesthetic artifact of, say, your OCD or your secret fetish to work in an operating theater. Most importantly, you know where stuff goes because you know where your brain will want to look for it at the right time later on, right? And, as you eventually learn, if you can't immediately grok whether a given piece of paper is trash, actionable, or just for reference, you will be, as Walter Sobchak says, "entering a world of pain."

Like Martin Ternouth's excellent paper-based system, Chanpory's tips encourage you to build fences between projects and tall walls between statuses. For example, think about how a frequent usage of an "Incubate Box" might change the chaotic state of your thinking (as expressed in the mystery-meat piles on your desk):

Holidaying Pope criticises overwork - The Herald

Words of wisdom from the vacationing Pope:

During his traditional weekly appearance to bless the faithful, Benedict XVI quoted from writings of St Bernard in the 12th century meant for popes of his time on the subject of overwork.

The saint advised pontiffs to "watch out for the dangers of an excessive activity, whatever... the job that you hold, because many jobs often lead to the 'hardening of the heart', as well as 'suffering of the spirit, loss of intelligence'," Benedict said, quoting St Bernard.

Bokardo » Apple Making Huge Social Software Push?

Via Andy, here's a thought-provoking post that draws from a mosaic of current and forthcoming features (including Wiki Server, iCal Calendar Sharing and the nifty-sounding Teams) to suggest that Apple's moving toward some interesting directions in social software and enhanced functionality for teams.

Joshua writes:

Notice that all of these features are about enabling communication as much as they are about creating content. It’s about getting the right information to the right person at the right time through interaction with their friends and associates. That’s how we do things out here in meatspace, so that’s how we’ll do things in cyberspace as well.

I think this is good news for Apple. As the proliferation of telephones, cellphones, chat software, blogs, and social networking sites have shown, there seems to be a market for this social software stuff…