UTC is a perfect system for machines. It is a single, continuous count of seconds from a fixed reference point. It does not shift with seasons. It does not vary by location. Two events timestamped in UTC can be sequenced accurately regardless of where the systems that recorded them are located. For infrastructure, logging, and any application where time is being computed rather than communicated, UTC is correct.
Humans do not experience time this way.
Humans experience time as local, relational, and contextual. "Next Tuesday morning" is a meaningful phrase to a human and an unresolvable ambiguity to a machine. It requires knowing the speaker's timezone, their definition of "morning," whether "next" means the coming Tuesday or the one after, and whether any DST transitions occur between now and then. None of that information is in the phrase itself.
This gap between machine time and human time is not going to close. It is not a temporary problem waiting for a technical solution. Humans will continue to write "next Tuesday morning" because that phrase accurately communicates what they mean to other humans in the same context. Machines will continue to require UTC offsets because that is what allows them to reason about time correctly. The interface between the two will always require interpretation.
What changes over time is the quality of that interpretation. Twenty years ago, resolving "next Wednesday at 9am CST" required manual lookup and human judgment. Today, it is possible to automate much of that interpretation — detecting the time expression, identifying the abbreviation, flagging ambiguities, applying the correct DST rule for the specific date, and returning a plain-English explanation of what was assumed and why.
The automation does not eliminate the gap. It bridges it. It takes a human-written time reference and produces a machine-verifiable result, with the reasoning shown. That is the function of a time interpretation tool — not to replace human communication with UTC, but to reliably translate between the two.
UTC and natural language are not in conflict. They are appropriate for different contexts. The problem is the moments when one bleeds into the other — when a human-written phrase needs to be treated as a precise timestamp, or when a UTC value needs to be communicated to a human audience. Those are the moments where interpretation matters, and where silent assumptions cause the most damage.