* Drift between terresterial and sidereal time,
* Drift between terresterial ground level (1G gravity mean 'surface') and orbiting satellite (eg: GPS time)
* Differing frames of time reference best suited for different tasks.
Common computer time server synced time is based on the nominal notion of "mean noontime" UTC .. or the rotation time of the earth to move from Greenwich "pointing at the sun" to again "point at the sun" (perhaps surprising to some NOT a full "360 degree" rotation as the earth has moved forward on its orbit).
Myths about time that programmers should know is a good read .. eventually drift between systems must be addressed ( GPS sats use "epoch time" (local atomic clock ticks) lapsed "per week" and GPS recievers reconcile relativistic drift using broadcast corrections ).
Any significant scientific data collection program (geophysics, astronomy) required the use of some form of "epoch time" with accurate local clocks not synced to UT | GMT | Zulu time servers.
Your apparent desire to not deal with adjustments on the order of a second during your lifetime is simply pushing the problem down the road until it's a case of reconciling hours .. or even 11 days (as has already happened in history).