If you could erase one event from history, what would it be?
Every developer knows there are two ways to deal with a commit they regret.
A commit is a recorded change in a project’s history—a decision or action that has been saved and can be traced.
Reset moves the branch pointer backwards, so the unwanted commit is no longer part of the branch’s current visible history. Revert leaves the original commit in the history but adds a new commit that reverses its changes.
The mistake remains in the record, but its effects are undone.
Reset erases. Revert redeems.
Today’s writing prompt asked: If you could erase one event from history, what would it be?
The question took me somewhere I did not expect—into the architecture of undo, and then into an empty tomb where the scars had not been removed either.
Ctrl+Z: The Undo Stack of History
If you could erase one event from history, what would it be?
Press Ctrl+Z on Windows or Command+Z on a Mac, and the most recent action disappears. But an
undo stack is not a time machine. It is a sequence of actions, and you can only undo them from the top.
History is much the same.
Suppose you choose a war. To erase it, you would also have to undo everything that came after it—the treaty, the borders, the institutions, the lives shaped by it, the books written because of it, and generations that would never have existed in quite the same way.
You cannot simply remove one event from history without disturbing everything built upon it.
The operation we imagine is not really available.
Not because it is forbidden.
Because history has no Ctrl+Z.
The Things We Cannot Undo
Some actions never enter an undo stack at all.
A sent email cannot be unsent from another person’s memory. A spoken word cannot be taken back
after it has wounded someone. A decision, once released into the world, may set events in motion that we can no longer control.
The events we most want to erase are often precisely those that cannot be undone.
The lorry has passed.
The word has been heard.
The plane has taken off.And history does not provide an undo button.
Revert, Not Reset
But Git offers another possibility.
git reset moves the branch pointer backwards, leaving the unwanted commit outside the branch’s current history. git revert does something more remarkable: it leaves the wrong commit in the history and adds another commit that reverses its effect. Anyone reading the history later can see both: the wrong—and the answer to the wrong. That distinction changes how I think about the past.
Reset erases. Revert redeems.
And once you see that distinction, Scripture begins to look different.
Joseph’s brothers really did throw him into the pit. Their evil is not erased from the story. Yet Joseph could say:
“You meant evil against me; but God meant it unto good.”
— Genesis 50:20
The first event remains.
But it does not have the final word.
Nothing is erased. Everything is answered.
The Scars in the Commit History
And then we come to the empty tomb.
The Resurrection was not a reset. Jesus did not return as though Good Friday had never happened.
He still carried the wounds. Thomas recognised Him by those wounds. Revelation presents the Lamb as one who had been slain.
The scars were not evidence that the miracle had failed.
They were evidence that redemption had happened.
God could have erased the wounds. Instead, He carried them into glory.
That may be the deepest answer to the question of whether history can be erased.
Perhaps the greater miracle is not erasure, but redemption.
What This Leaves Us Holding
I do not mean that everything that happens is secretly good. Some things are monstrous. Some wounds remain painful. Some losses can never be explained away.
I simply mean that the past does not have to be erased for the future to be redeemed.
Your history may contain a commit you would give almost anything to reset—the year, the letter, the decision, the sentence spoken in a kitchen.You know its hash.
You could find it in the dark.
It will not be reset.
But it can be reverted—answered, overruled, transformed, and perhaps even made into the place where you are recognised.
And here is the extraordinary thing about redemption:
The repair is visible precisely because the wound remains in the record.
Take away the wound, and you also take away the evidence that anything was healed.
So perhaps the Christian answer to the past is not:
“It never happened.”
It is:
“It happened—and grace wrote what came next.”
God does not press Ctrl+Z. He redeems.
Closing Question
What is the commit you would reset—and what would it mean to discover that it could be redeemed instead?
Scripture referred to: Genesis 50:20; Luke 22:42; John 20:27; Revelation 5:6.
John Britto Kurusumuthu | Rise & Inspire | riseandinspire.co.in
Written in response to the WordPress Daily Writing Prompt for 19 August 2026.
Explore more at the Rise & Inspire archive | Daily Prompts
© 2026 Rise & Inspire.
Website: Home | Blog | About Us | Contact| Resources
Word Count:878
Discover more from Rise & Inspire
Subscribe to get the latest posts sent to your email.
