Skip to main content

Book Review: Getting Things Done by David Allen

I often write a reason why I picked up the book but this time I am not sure. Probably it was just easiest-looking on on the kindle. Turns out it is not that easy to read as I thought, especially if you compare it to  "Decisive". Soon after I started, I could feel that book was written at 2002 when PDA were today's smartphones. I would also say that book would be much nicer if it was more concise and contained more stories.

The book is a bestseller for a reason though.

"What is the next action?"
It is probably the most important question in the book. I have the same problem. My todo list is not really todo. It is just list of "stuff". Asking for next physical action really changes the way you think and work.

Second important idea form the book is to group tasks by context. Most important constraint is context. I have different list for 'home', 'work' and 'commute' as for example I need guitar to practice.

Last idea is about "Someday/Maybe" list. I had something like this working, but it was great to read more about how author is using it and tweak it a bit.

Rating: 6/10


Popular posts from this blog

How to simulate slow connection (developer proxy in Node.js)

Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy.

Toggle device modeChoose Network type.Refresh the page 


For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me.

I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one.

With this module I can write really short code to create slow server:

var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host: 'localhost', port: 8080, …

How to use NPM packages from private repositories on bitbucket

Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public but still want to have an ability to install them easily.

After googling and experimenting I have found simple solution.
First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important.

Change example from below to:
user - username
PASS - password of the user
organization - owner of the project (you can find it in bitbucket url to your project)
project - your project name