Ruby Video
Talks
Speakers
Events
Topics
Leaderboard
Sign in
Talks
Speakers
Events
Topics
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By, Katherine Wu For developers, there are two things that are certain for time zones: you can’t avoid having to deal with them, and you will screw them up at some point. There are, however, some ways to mitigate the pain. This talk will discuss tactics for avoiding time zone mayhem, using a feature to send out weekly email reports in a customer’s local time zone as a case study. It will cover idiosyncrasies of how time zones are handled in Ruby and Rails, how to write tests to avoid false positives, and advice on how to release time zone-related code changes more safely.
Date
Summary
Markdown supported
In her talk at RailsConf 2015, Katherine Wu tackles the complex topic of time zones, a frequent challenge for developers. She shares insights and strategies to mitigate the frustrations caused by time zone discrepancies in software coding and project management. Key Points: - **Complexity of Time Zones**: Wu discusses why time zones can be difficult to manage, highlighting issues like government changes in daylight saving time and the historical context of timekeeping that can confuse project timelines. - **Historical Anecdote**: An example from October 1582 is noted, where a calendar transition led to the skipping of days, illustrating how timekeeping has evolved and remains confusing. - **Misconceptions About Time Zones**: Wu points out common misconceptions such as the belief in a uniform distribution of time zones and the existence of zones that differ by more than one hour. - **Practical Example**: She describes her company's challenge in sending weekly email reports to a global customer base, emphasizing the customer's expectations of receiving reports at local times. The solution involved scheduling reports for 10 AM local time on Mondays, requiring adjustments to the sending processes to avoid confusion. - **Tools and Libraries**: Wu recommends using libraries like 'TZinfo' for effective time zone management in code and emphasizes the importance of staying updated with changes in daylight saving time and local time shifts. - **Testing Strategies**: Emphasis is placed on the need for disciplined testing practices to ensure accurate time reporting, which includes clear setups for maintaining the integrity of the test case. - **Best Practices**: She concludes with best practices such as maintaining backups, learning from mistakes, and developing a comprehensive understanding of time zones to improve coding practices. In summary, Wu encourages developers to view time zones not merely as obstacles but as integral parts of their projects that require careful handling. She provides a framework for approaching time zone-related challenges and emphasizes ongoing learning from past experiences to enhance future coding endeavors. Her insights are aimed at easing the common burdens time zones pose in software development, making the process smoother and more reliable.
Suggest modifications
Cancel