You Changed the Date. The Article Still Thinks It's September.

You Changed the Date. The Article Still Thinks It's September.

A few weeks ago I gave a batch of new posts staggered publish dates going back over the previous month, so the site looked like it had been posting steadily instead of in one dump. A routine thing. Rewrite the date field, done.

One of those posts opened with "It is mid-September, with about fifteen weeks left in the year." Its new date was August 25.

The obvious fix, and the one it missed

My assistant searched the posts for month names and found that opening line. It changed "mid-September" to "late August" and "fifteen weeks" to "eighteen weeks". Clean edit, committed.

Two paragraphs later, the same post said "those fifteen weeks". No month name. No date. Just a number that referred back to the opening sentence it no longer matched.

The search for month names could never have found that line. There was no month in it. We only caught it because I re-read the whole edited section after the commit, half out of habit, and the number looked wrong.

Derived facts

A date is not one fact in an article. It is the root of a small tree of facts that are computed from it and never labeled as such.

  • Durations: "fifteen weeks left", "three months since".
  • Counts: "the fourth post this month".
  • Seasons and weather: "now that it's cooling down".
  • Relative references: "last week's post", "next month".
  • Anything that says "now", "today", "currently", "this year".

Change the root and every one of those is stale, but none of them contain the word you searched for. The second "fifteen weeks" was the giveaway in this case because it reused a number. A sentence like "that leaves plenty of the year" would have survived every search I could think of and still been wrong.

How I do it now

Search for the numbers you changed, not just the words that prompted the change. If "fifteen" became "eighteen", grep for "fifteen" across the whole post afterwards. The derived reference usually repeats the derived value, not the source.

Re-read the whole section around every edit, after the edit. Not the line. The section. Derived facts live within a few paragraphs of their root because that is where the writer's mind still had the date in it.

Treat backdating as a rewrite, not a field change. Before touching the date, read the post once asking only "what does this sentence know about when it was written?" Mark every hit. Then change the date and fix the marks. That is the order that works. Doing the date first and hunting afterwards means you are searching for things you have not yet noticed.

Better still, write posts that do not know what day it is. "In September 2026" survives any date change. "This month" does not. Absolute dates are slightly clunkier to read and far cheaper to maintain.

The assistant did exactly what I asked

I want to be fair to the tool here. I said "fix the date references" and it fixed the date references. The problem was my model of what a date reference is. It is the same mistake as grepping for a function's name after a refactor and missing the place that calls it through a variable. The thing you are looking for does not always carry the label you are looking with.

The post is correct now. I think.