Writing about time
Four write-ups on why counting time goes wrong: which days a date difference includes at either end, how to add shift times without turning 1:45 into 1.45, whether the Pomodoro technique survives scrutiny, and what a visible countdown does to behaviour.
Time
How to Schedule a Meeting Across Timezones
Anchor the meeting to one named zone, check whether daylight saving changes between now and the date, and write the invitation so it cannot be misread.
Read
Time
How to Estimate Work in Hours Without Lying
An hour estimate is a guess about focused time, not a clock. Why it runs short, why a buffer on every task backfires, and how one recorded week gives you your own multiplier.
Read
Time
How Leap Years Actually Work
Every fourth year, except centuries, unless the century divides by 400. Why the rule exists, what 1582 skipped, and the bugs a 29 February keeps causing.
Read
Time
Why a Visible Countdown Helps You Focus
A timer you can see is a decision you already made. What that actually buys you, how long to set it, and the three things it will not fix.
Read
Time
How Many Days Between Two Dates: Two Right Answers
The arithmetic is easy. Deciding whether the end date counts is the part that trips everyone up.
Read
Time
How to Add Up Hours Worked Without Errors
Convert every shift to minutes, subtract the breaks, divide by 60 at the very end. Plus the decimal trap that shortens your week without your noticing.
Read
Time
Does the Pomodoro Technique Actually Work?
The bounded session and the forced stop hold up. The number 25 does not, and the two rules that make it a method are the ones everyone drops.
ReadWhere to start
How to estimate work in hours is the one with the widest reach, because almost everyone estimates something and almost everyone is systematically optimistic about it in the same direction.
Does the Pomodoro technique work is the one that tries hardest to be honest about the evidence rather than repeating the claim.
What these pieces have in common
Time is the one quantity everybody is fluent in and almost nobody calculates correctly, because its units are irregular in a way no other measurement is. Months have different lengths. Hours are base 60 while every spreadsheet is base 10. Years occasionally have an extra day, by a rule more complicated than the one most people remember.
How leap years actually work is the clearest example: divisible by four, except centuries, except centuries divisible by four hundred. The other pieces here cover the arithmetic that goes wrong in practice, such as counting days between dates and adding up hours worked, and the psychological side in why a visible countdown works.
Frequently asked questions
What is the actual leap year rule?
A year is a leap year if it divides by four, unless it also divides by 100, unless it divides by 400. So 1900 was not a leap year and 2000 was. The correction exists because a solar year is about 365.2422 days, and adding a day every four years overshoots slightly.
Why do people underestimate how long work will take?
It is a well documented bias: people estimate from the path where nothing goes wrong, because that is the version they can picture in detail. Interruptions, rework and waiting on other people are real and recurring, and they are absent from the mental model that produces the number.
Does the Pomodoro technique have evidence behind it?
The general principle that breaks help sustained attention is supported. The specific twenty five minute block is not a research finding, it was the duration of a kitchen timer. The useful part is deciding in advance when to stop, which works whether the interval is twenty five minutes or fifty.
All categories
PDF 10Images 10Text 14Design 11Security 8Calculators 13Developer 20Everyday 4