The book that saved my life
Well, not literally, but maybe saved my sanity. The last 6 months has kind of been a blur, with loads of different things going, both at work and home (especially work), as I tried to get used to the new job title, still keeping up with the old job(s), and generally trying to make some progress. Somedays it just felt like there was way too much going on.
This last couple of weeks things got pretty stressful, so by a complete fluke, Getting Things Done
was the next book on my reading list. Combined with new found passion for reading, based solely on having my fantastic and shiny new Kindle in hand, I've pulled a couple of things into my daily schedule that mean I'm keeping up with everything going on a lot better. I still haven't finished the whole thing, and still have plenty of work to do before I'm following all of the steps, but I'm getting there, and this week has definitely been a lot better than 2 weeks ago. Progress is a wonderful thing.
posted by Aaron at
12:52 PM
2 Comments:
I read this myself a year or two back, and I thought it makes a bunch of sense.
In a way, it's the same sort of principles as you'd apply to any rationalisation, be it software design and optimisation, or business process engineering. ie. Don't Repeat Yourself (either by data duplication or redundant processing)
Applying the same sort of tidying to the data flows that form your personal chores, projects and to-do lists, and you'll pretty much converge on a solution close to what he describes here.
So the specifics of what he suggests aren't necessarily earth shattering. But the implication of overcoming ingrained personal habits of inefficiency is a big deal.
Coolio!
Mate, out of all the people I know in the whole world who I thought would have read this, you're not one of them ;-)
Just for curiosities sake, did you read this before or after the "rings gone missing" incident in Ravello?
Post a Comment
<< Home