by Asim Jalis, MetaProse.com
The MicroTask process is a technique for taking on large and vague projects and then gradually nibbling on them until they are done.
Besides getting things done, this technique will make your work fun. It will turn it into a game. Instead of working on a large and intimidating goal you focus on mindlessly small and trivial steps. And then before you know it the whole thing is done.
The best way to illustrate things is with an example. To use this technique all you need is a simple text editor such as Vim.
Here what to do.
-
Make a list of all the tasks you can think of on top and put them under the heading Remaining Tasks.
-
Pick a task to work on.
-
Copy the title of the selected task below the Remaining Tasks section and then add notes about the task there.
-
Each time you’re done with a task put an “x” on it and push down the notes related to it lower into the file. The top of the file is all you need to look at to figure out what you’re currently working on.
-
When you have a lot of done tasks move them to the end of the file into the Done Tasks section. The “x” makes it easy to visually mark and ignore the done tasks.
Remaining Tasks
x Find the ABC bug
x Read through the bug
x Ask Phineas + Ferb: Why did the process fail? What are next steps?
x Find obliterate.sql
Analyze obliterate.sql and guess why it fails
Search the logs for messages about obliterate.sql
Find out where obliterate_prepare is being called
Ping Phineas + Ferb again after 4:45 PM
Visit Phineas + Ferb on the 1th floor
Show them the fix and get their feedback
Compile the fix
Verify that the fix worked
Check in the fix
Close the bug
Find obliterate.sql
The file exists at doofenshmirtz/dangerous/scripts/obliterate.sql
Ask Phineas + Ferb: Why did the process fail? What are next steps?
They said there was an assertion failure in obliterate.sql.
Find the ABC bug
The bug is at http://bugdb/bug/1234
Done Tasks
[Add done tasks here]