productivity - Should a programmer try to list their "Next Actions"? -


David Allen's "getting things" recommends keeping a "next action" list to organize your work, where "next action" is the next physical action that you will make to progress towards any purpose.

In programming, to determine what to do next, it is often difficult to do this (seems like a problem of exhaustion). Most of the tasks are examining the program to determine how and how to modify the code to get some purpose. Body type is easy to write code. Once you know what to do, why can you try it in a few minutes, why stop it to describe it?

Is the next action list a useful way to organize programming work? If so, how would you define your next action? If not, then whatever you want to do, how do you organize it?

There is a related question.

Once you know what to do, why try it in a few minutes Why can you stop to describe it?

Sometimes whatsoever thinks a few minutes may be a few days, if not, "only a small thing here and there" which is not very little at the end.

Is the next task list useful? How to organize programming work?

I think it can work if someone has a stick with it and a stick of habit.

If so, do you have your next action?

I define it as the next step and I should know that it is done. It can be as simple as knowing which class I am building or what I want to give to some exams. It can sometimes be useful to go back and what happens in the list when Someone wants to do something, if blocked by a bug.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -