To get back into rails and ruby. I don't spend enough time here.
To use rails 3.1 and the assets pipeline.
To learn Backbone.js.
To write tests.
"I am not a great programmer. I am just a good programmer, with great habits." -- Kent Beck
- To be simple and clean.
- A backlog List
- Todo Today List
- Ability to Estimate Work
- A timer that is "wound up"
- Ability to track internal and external interruptions.
- A graph that can be printed and emailed.
- A simple REST based api so that other applications can interface.
Ideas I am toying with
- Socket based timer. This would allow the user to 'accidently' close the page and come back without losing the pomodoro.
- Allow team based timers. This would involve sockets as well.
Taken From Appendix 1 of "The Pomodoro Technique"
- A Pomodoro Consists of 25 minutes Plus a Five-Minute Break (§2.1).
- After Every Four Pomodoros Comes a 15-30 Minute Break (§2.1.2).
- The Pomodoro Is Indivisible. There are no half or quarter Pomodoros (§2.1).
- If a Pomodoro Begins, It Has to Ring:
- If a Pomodoro is interrupted definitively – i.e. the interruption isn’t handled (§2.2.2) – it’s considered void, never begun, and it can’t be recorded with an X (§2.1.1).
- If an activity is completed once a Pomodoro has already begun, continue reviewing the same activity until the Pomodoro rings (§2.1.3).
- Protect the Pomodoro (§2.2.3). Inform effectively, negotiate quickly to reschedule the interruption, call back the person who interrupted you as agreed.
- If It Lasts More Than 5-7 Pomodoros, Break It Down (§2.3, §3.11, §4.2). Complex activities should be divided into several activities.
- If It Lasts Less Than One Pomodoro, Add It Up (§2.3, §4.2). Simple tasks can be combined.
- Results Are Achieved Pomodoro after Pomodoro (§3.8).
- The Next Pomodoro Will Go Better (§3.9).