I wanted to address a couple criticisms that get made about producticity plans in general and Getting Things Done in particular.

Not to mount a big defense, exactly, but I think there are good points to mention and discuss because they contain germs of insight about whether and how you can actually improve yourself.

Jon Udell's bookmarklet is a Top 10 lifehack.

"...maybe what the man page for an immaculate apartment might look like..."

As a kind of addendum to the previous post on hacking Getting Things Done , I thought I’d share my Hamburger Helper template for a new GTD list. It’s pretty underwhelming, I have to admit, but it has a few features that are kind of neat.

gtd_template.txt

Productivity programs like Getting Things Done obviously have been developed around the needs of managers, sales people, and entrepreneurs. This makes sense given that those are largely the people who are buying the books, listening to the CDs, and attending the seminars (or certainly represent the largest market share of potential customers).

But, one of my main goals with this site was to discuss the way that productivity plans and methods designed for the business world can be reframed in a context that's useful for developers, programmers, and garden-variety geeks. This is not to say that geeks don't fill many or all of these managerial roles in their work, but they also tend to have work styles, deliverables, and skillsets that are markedly different from the average, notional GTD user.

The prime example: "@computer." Man, geeks don't just use a computer for occasional work or to "look something up on 'The Interweb.'" They live on their laptop and take it anywhere they'd bring their wallet. They eat wireless like potato chips and crank out code for a living. They have an IM window and an IRC channel running all day. They're streaming conferences in and live-blogging conferences out. In short, if they follow the stock GTD setup, they will have a very, very long "@computer" list.

So I wanted to start a conversation about how geeks handle their lists, their projects, and their agendas--not so much in terms of the tool they use to store the information, although that's fair game--as with how they segment the information and decide when to break it into pieces. I'll start by providing the setup used by a San Francisco web developer who spends a lot of time on his PowerBook: me.

(Please note: since I'd love to see a lot of discussion about this, please post your response on your own site and just send a single trackback ping to this post (hit: http://www.typepad.com/t/trackback/1128456). Comments below are ok for short responses or for posting links to your non-tracback-able site, but please try to limit yourself to a paragraph or so. Thanks.)

It’s Saturday night and time to clear out my inbox. Here’s a hodgepodge of little tips, tricks, hacks, and unsolicited advice.

A photo, a burger, and a short story about patronizing the neighborhood.

Shawn Medero suggested the subject of using OSX labels to get organized.

Here’s a quick tip: think of labels less as ornamentation or overly-specific vertical tags. Think of your labels as a system of functional markers that complement your existing organizational system—that provide information you might want during a search, backup, or time-based script events and reviews as an example.

I often end up using my Desktop as a parking lot for current files. Not exactly an inbox, but given how easy it is to hit CMD-D in a dialog box, it’s where a lot of tmp files, exported jpgs, and assorted stuff naturally ends up. Still, I find it distratcting when too much stuff accumulates there, so I also keep a “Junk” folder on the desktop.