How to implement GTD for university students

Meeting Tip: Learning Names | Gurno.com

As someone who suffers from frequent encoding errors and buffer overflows, I love Adam's idea to start a meeting by mapping the name and location of each attendant, along with their title, etc. Adam writes:

Step 1 - Reconnoiter

Draw a quick map of the table/layout of the meeting. Place yourself on it, to give yourself a reference point.

Step 2: The Combatants

As people introduce themselves around the table, fill them in. If you feel last names are necessary add those too, but don't do it at the expense of writing down someone else's name. You can guess at the last names later. If you miss one, leave it blank and fill it in as soon as you can - if someone else refers to them, etc, etc.

Not all tasks are created equal. Our to-dos all differ in priority, complexity, time requirement, and context, so it’s probably daft to always capture and expose them in an identical way. I have a little trick for dealing with this that’s been working really well for me.

Back in the day, my to-do list was an egalitarian nightmare of inefficiency — verb-centric “next actions” through they all were, I commonly faced a task list that looked something like this:

• call Alice about Foo project
• fix line 125 of bar.php
• fix line 349 of bat.php
• take out kitchen recycling
• buy milk
• buy index cards
• sweep the decks

Now, the problem here might be self-evident to you smarter people, but I was missing an important concept: there is such a thing as too granular a task to track as its own event. In this instance, I was cruftifying my landscape with items that were way too detailed or tiny and, consequently, I’d turned my task list into an undoable roller coaster of un-focus. Just as “projects” are composed of “tasks,” I like to think that “tasks” themselves can often be collected into silos of small “mosquito tasks.” And my solution, as ever: text files and alarms.

the Scarlet Letters: Notes on Making Art

This is a terrific bunch of notes on hacking your creative process, especially as it applies to visual art.

I really love the idea of not getting hung up on your failures and trying always to make rather than judge as the process is underway. It reminds me favorably of what Anne Lamott says about fearlessly producing your “shitty first draft.”

A few of the points I especially enjoyed:

stevenf.com ("Don't Use FTP")

Steven Frank, one of the boys wonder behind Panic and their excellent Transmit app says it’s high time to dump FTP in favor of its smarter, sexier sister, SFTP. Of which Steven says “It’s secure, it’s consistently implemented, and it’s machine-readable.”

A lot of people who have used FTP daily for years are surprised to learn that they're sending everything in the clear -- that means the stuff you're uploading as well as your actual password. Makes you think twice about what you're throwing through the air as you update your blog templates via "free WiFi."

Steven says:

I always try to credit the source for stuff that I link to when I've learned about it from other sites. In addition to helping my readers connect with voices they may not have heard before, I believe it's just the classy thing to do. (I'm looking at you, "A Listers" -- a lot of you have started dropping vias for everyone but your highest-profile buddies: tacky, tacky).

Anyway, I admit that I'm not 100% either, but in the interest of trying to make good, here are a few of the sites that I find myself reading and linking to a lot. Thanks to their authors and contributors for sending me (and you) to so many interesting places.

For a while now, Transmit -- my hands-down choice for all things FTP -- has had a feature that I adore, which is the ability to edit text files from a remote server directly in the local Mac editor of my choice (in my case, that's the very swell TextMate. This little bit of wizardry makes it really easy to quickly fix code, tweak style sheets, or correct spelling without that nightmarish 90s ritual of the re-re-re-re-reupload (which is particularly painful when you're working on a live application).

Well, heck. I just figured out that the latest version of Transmit takes this to a another (yes! yet! another!) level by letting you edit images on a remote server. I just opened a .png in Photoshop and saw the saved results immediately appear on the live box. Disco.

As a consequence of being too lazy to take the trash out a couple nights ago, the smell of salmon took up residence throughout our kitchen. In addressing the stank, I ran across this ginormous page full of of links on cleaning and stain removal including a handy collection of homemade air fresheners.

When the iPhone came out this summer, I was locked into a contract with another cell phone carrier, one that I couldn't escape on pain of a $200 surcharge. So I waited it out, and dreamed my little iPhone dreams all alone with my Plain Jane cell phone and suddenly archaic-looking iPod Video.

To be honest, I didn't really need an iPhone. I work from home, rarely more than a few yards from a computer (we had two laptops and a Mini in our house at the time). I don't travel for work, and when we go on vacation, I never bring work with me anyway. When I do leave the house for extended periods of time during the day, running errands, taking appointments, etc, it doesn't matter because I'd trained myself to plan ahead for that situation. Besides, I never get any messages that can't wait a couple hours until I get back to a computer anyway.

I was amazingly good at rationalizing away my need for an iPhone, but I still wanted one ever so badly. So last week I created a way out.