• I have already build simplegtd.com. But personally, I want more, I mean less.

• I have added features that I didn’t need, but were requested by others. Like linking actions to project.

• I want something thats simpler, which will helps me focus on one thing at a time and guided me through the daily and weekly review process and has a manageable “Some Day / May Be” List.

• So I have decided to build “SimplerGTD” for myself, by following the steps listed in How should I be building software for myself?. And will be posting all my progress here.

– To simplicity & beyond!

A few fundamental principles:

• Clarity and simplicity are of paramount importance. The user of a module should never be surprised by its behavior.
• Modules should be as small as possible but no smaller.
• Code should be reused rather than copied.
• The dependencies between modules should be kept to a minimum.
• Errors should be detected as soon as possible after they are made, ideally at compile time.

While the above rules do not apply 100 percent of the time, they do characterize best programming practices in the great majority of cases. One should not slavishly follow these rules, but violate them only occasionally and with good reason. Learning the art of programming, like most other disciplines, consists of first learning the rules and then learning when to break them.

Paraphrased form the introduction chapter.