Pomodoro Timer

What this tool is used for

• Working in fixed intervals when a task is large enough to be avoided.
• Tracking how many focused sessions a piece of work actually took.
• Building in regular breaks that you would otherwise skip.
• Timeboxing an open-ended investigation so it does not consume a day.
• Structuring a study or review session with predictable pauses.

Frequently Asked Questions

What is the actual Pomodoro Technique?

Francesco Cirillo's method from the late 1980s: 25 minutes of single-task work, a 5-minute break, and a longer 15-30 minute break after four cycles. Named after the tomato-shaped kitchen timer he used as a student.

Is 25 minutes special?

Not physiologically — it was chosen as short enough to feel unintimidating and long enough to be useful. The method's own guidance is to adjust it; 50/10 suits deeper work, and shorter blocks suit tasks you are avoiding.

What if I am interrupted?

The original rule is strict: an interrupted pomodoro is void, not paused. That severity is deliberate — it makes the cost of interruption visible, which is the behavioural point rather than an accounting one.

Does the timer keep running in a background tab?

Browsers throttle timers in inactive tabs, so a naive setInterval drifts badly. A correct implementation computes elapsed time from a timestamp rather than counting ticks, which stays accurate regardless of throttling.

Why breaks rather than working straight through?

Sustained attention degrades measurably over time, and brief diversion restores it. The breaks are load-bearing — skipping them turns the method into ordinary uninterrupted work with a timer attached.

How should the technique adapt to deep work?

By lengthening the interval. Twenty-five minutes suits tasks with a natural stopping point, but work requiring sustained context often loses more to the interruption than the break returns — 50 or 90 minute cycles are a common adaptation.

Why does writing down the interruption help?

Because the value is in not switching. Capturing the thought and returning to it at the break preserves the context you already loaded, which is the expensive part — the technique is really an interruption protocol.

Should a browser tab be trusted to notify me?

Only with the tab audible or notifications granted. Background throttling can delay a timer callback by seconds, and a silent tab may not surface anything at all — which is why the audible cue matters more than the countdown.

Common errors and gotchas

• Treating the interval as a rule rather than a tool, and breaking a productive flow to obey the timer.
• Skipping breaks, which removes the part of the technique that makes the intervals sustainable.
• Counting a session as focused when it was spent on interruptions.
• Closing the tab and losing the session count, since the state lives in the page.
• Using it for work that genuinely needs long uninterrupted blocks.