I think one of the most frustrating messages you can encounter online is:
"Your session has expired."
Especially when you realize that the 15 minutes you just spent filling out a form have apparently expired along with it. :)
You've spent considerable time completing a lengthy form. You're almost at the finish line when your phone rings. You step away for a couple of minutes, come back, and discover that everything you've entered is gone.
From the system's perspective, nothing particularly unusual happened. A session simply expired.
But from the user's perspective, 15 minutes of their life just disappeared.
What I find interesting is how much time we invest in software development: performance, architecture, UI design, optimization, scalability, and countless technical details.
Yet sometimes, we forget something fundamental:
People don't use our products under perfect laboratory conditions.
Their phones ring in the middle of a task. Their internet connections drop. They accidentally close a browser tab. They get distracted. Sometimes, they even click the same button twice.
These aren't exceptional circumstances. They're everyday realities.
And I believe well-engineered software should be designed to handle them gracefully.
For example:
- When a connection drops, users shouldn't have to enter everything again.
- When someone clicks "Submit" and the interface becomes unresponsive, they shouldn't have to guess whether their request was successfully processed.
- When users navigate away and return, their non-sensitive input should ideally still be available.
- When an action is accidentally triggered twice, the system should be designed to prevent unintended duplicate operations.
Of course, implementing these behaviors isn't always straightforward.
There are legitimate technical challenges involving data security, session management, state persistence, request idempotency, consistency, and recovery mechanisms.
But those complexities are our responsibility as engineers, not the user's burden to carry.
After all, the fundamental purpose of automation is to simplify processes, reduce unnecessary effort, and make people's lives easier.
Users shouldn't need to understand what happens behind a button.
And they certainly shouldn't have to suffer because of what happens behind it.
I'm Amirhossein (Amir Hossein) Moloudi, and I'd genuinely welcome perspectives, experiences, and constructive criticism from anyone who comes across this post.
I believe that, especially in the age of AI, these seemingly small engineering decisions are becoming increasingly important.
As building software becomes easier, building software that genuinely respects people's time, attention, and trust becomes an even more meaningful differentiator.
