Wow. It's been over nine months since I quit Entourage in favor of the kGTD/iCal productivity tag-team. In that time, I could have had an infant, finished a school year, or been responsible for a couple failed sitcoms. (I mean: if I had a uterus, was still in college, and were, say, McLean Stevenson)

Yes, friends, I do still spend a lot of my day shaking my hammy fist in impotent rage at iCal's numerous shortcomings, but I've reached a kind of détente with Apple's stock calendaring app, and along the way I've discovered some modest ways to squeeze more drops of Cupertino-y goodness from its moist Jolly Rancher-like pages. Here's a few of my favorites.

• Getting more out of iCal - "The truth is, iCal works great with kGTD (mostly of course), and once you make your peace with the perplexing stasis of its feature set, there are some not-bad hooks and affordances hiding in its pastel, roundy corners. Here’s a few I like."
• HOWTO: Flag “penciled-in” events in iCal - "When I create the event, I just put a Spanish-language question mark “¿” (hit: OPTION-SHIFT-?) in front of the event’s title. Like so..."
• Schedule (and choose) a dash in iCal "If you start the name of the task with the number of minutes in the dash, you have a very easy to way to see items that can be knocked down quickly (hint: sort “To Dos by Title”)."
• Dr. Contextlove or: “How I stopped worrying and learned to love iCal” - "But why bother with organizing these into meta-groups? Ah, because it makes it so easy to reveal or hide all the tasks that I can work on at a given time, just by ticking the group’s little click box."
• Kinkless GTD .83: Enhances Quicksilver and iCal integration, much more "I really like to plan in kGTD and then do out of iCal since it reduces the amount of fiddling and meta work temptation. That doesn’t mean, however, that I wouldn’t benefit from a little extra backward integration."

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.

I'm working on an article about email tricks for one of your finer magazines, and -- as you might imagine -- when it comes to the inevitable Windows stuff, I'm a bit light in the useful tips department. So, I turn to you Redmond-using smarties for help.

Do you have a favorite application, plugin, trick, or hack for bending Windows email to your will? Double-credit for Outlook add-ons that garden-variety users can install without fancy root-style access. Whence comes your magic Windows fu?

Let Your Blog Posts Marinate (4 Steps to Forming Great Ideas) at LifeDev

Good advice on developing a tunnel for how you draft stuff that will eventually go on your blog. I think #3 ("Let it develop") -- while it could benefit from a bit more explanation -- is the really interesting part. Try not posting immediately, and return to the draft later on:

It’s hard to say how long this step lasts. Sometimes it’s all over in 15-20 minutes. Sometimes it takes weeks. The important thing is not to rush the process.

5ives: The text file behind the curtain

I do something similar with 5ives, where this kind of process is really conducive. I have a running, two-year-old collection of ideas, partial lists, orphan titles and lots of "one fun line I could build a good list around." Goofy as many of them are, some actually sat around since the site began until they evolved to the exact choices, wording, and order that I liked.

Tip: Use text folding

Since this kind of collection method can get messy (over 100 partial piles of junk in one text file), I like to use text folding inside TextMate. This makes it easy to "roll up" lists in such a way that just the title shows, then you can individually click a little "reveal" arrow to see the hoisted contents. Something like this (note the arrows in the gutter):

The beauty part is that I can still append text to the bottom (or prepend to the top) using Quicksilver since it's all just plain old text. Neato.

[ via Gina on Lifehacker ]

makezine.com: The Simplest Thing That Could Possibly Work

Danny and my latest column, for vol. 07 of Make, is about "The Simplest Thing That Could Possibly Work." While the concept is nothing new to agile developers, we wanted to talk about how it relates to the lives of garden-variety makers and life hackers:

When choosing an approach to building code that will pass their unit test, XP programmers are always encouraged by their beardy masters to "try the simplest thing that could possibly work." Note that this is not the most comprehensive thing that could work, nor the most impressive thing that could work, nor even a particularly enjoyable thing that would just be really fun to build...

[In Danny's Life Hacks research,] geeks weren't developing world-beating frameworks that could "scale across the enterprise" or cook a plate of french toast every morning -- most of the scripts were hastily coded with the single-minded purpose of fixing exactly one problem.

The geeks' consequent leaps in productivity seemed to come not simply from automating repetitive tasks, but, one imagines, from not blowing two weeks engineering a bloaty system meant to solve every conceivable problem in their lives.

Among many other cool things, this issue also has a profile on Mark Pauline, instructions on building a weatherproof wi-fi access point, plus -- my favorite -- three methods for silencing a child's beeping toy.

Vol. 7 of Make is available at your geekier magazine stands, or you can buy it now on Amazon.com.