Teaching myself not to procrastinate

re: Teaching myself not to procrastinate

Mad Martin — Sat, 20 Nov 2010 18:01:08 GMT

But, no matter how far you've traveled down the wrong road, it's always better to turn back. With one exception: If you can finish the project and then forget for good, you've got the choice, whether to pull through, or turn back.

When a choice is hard, i'll strart with the more elegant and possibly more complex approach and see where it takes me. Usually the first issues arise early and give you a lot more data to think over your choice. One or two major iterations are inevitable anyway, so you might as well experiment with the real thing.

What i find this blog entry didn't cover is the importance of the decision. How much difference in quality there is in relation to the whole project. Cutting the loading time in half is next to nothing if that time is only a few seconds.

What i also find a very important criteria is the work involved. Most of the decisions follow the 80/20 rule. If it produces a slightly better result it might be a lot more work. So the best choice is the one that just gets the job done.

re: Teaching myself not to procrastinate

Daniel Ray — Fri, 12 Nov 2010 14:37:50 GMT

Political beliefs aside, Bush's book is all about having to make a decision and simply sticking with it. Sometimes you're right and sometimes you're wrong. Put on the Nike shoes and Just Do It.

re: Teaching myself not to procrastinate

George Clingerman — Thu, 11 Nov 2010 21:01:17 GMT

Have you read Blink yet by Malcolm Gladwell? He covers this a bit in a few of his chapters and it's just generally a fairly interesting book on a very interesting topic (the art/act of making snap decisions).