Nice article!

People tend to avoid time tables relying on SQL functions. This is a good approach if you don't need to do those calculations frequently.

I remember a project where people wanted to kill me when I designed a table with time period and correspondent details as worked hours in that period and so on.

When somebody decided to change those periods from calendar months to something different, programmers got crazy and came to me to see what to do....

Just to hear all we had to do was to run a couple of UPDATE statements in the previously infamous time table 😀