Time as a concept, is something that lives between the real - the Earth orbiting the sun; the imagined - the calendars and the clock; and the purely subjective - the length of a techtalk.

As developers we need to balance both the conceptual understanding of time - in as much as giving an estimate of finished projects; and the factual - as in making models that are safe, and will stand the march of, as it were, time.

In this talk, we’ll trace the winding history of timekeeping — from Roman emperors and papal edits to spreadsheet bugs and legacy code. Along the way, we’ll look at how programming languages like JavaScript and C# inherited the chaos, and how we try (and fail) to tame it.

Whether you love history, hate time zones, or just want your app to handle daylight saving without breaking, this session includes history, bugs, regrets, and just enough practical advice to get you safely to the future.