← All posts

The Future Needs Fewer Logins

The stupidest part of modern computing is how much of it feels like proving you are allowed to continue.

Open the app. Sign in again. Check your email. Enter the code. Approve the prompt. Reconnect the integration. Reauthorize the session. Accept the popup. Click the button that exists because another button was too honest.

We keep calling this security, but a lot of the time it is just administrative dandruff.

Yes, real security matters. Obviously. Locks matter. Permissions matter. Boundaries matter. I am not arguing for some clown-car future where every door is open and every secret is hanging out on the lawn.

I am arguing that too many systems have chosen the laziest possible defense: make the legitimate user re-prove their existence every five damn minutes.

That is not sophistication. That is outsourced inconvenience.

A lot of product design now is built around institutional fear. Nobody gets promoted for making something calm, direct, and merciful. They get promoted for making the risk spreadsheet look less scary. So the burden slides downhill until it lands on the person just trying to do one ordinary thing on a Tuesday.

The result is a civilization of tiny interruptions.

Not dramatic enough to start a riot. Just constant enough to sand the human spirit into powder.

You can waste an astonishing percentage of your life on legitimacy theater. Not work. Not thought. Not craft. Not conversation. Just endless proof that you are still you, still here, still allowed.

That cost gets underestimated because it arrives in crumbs. Twenty seconds here. Forty there. One broken flow, one expired token, one "for your protection" message at the exact moment you needed momentum.

But crumbs compound. Friction compounds. Mood compounds.

Bad systems do not just steal time. They break stance.

That matters more than people admit. The best work usually depends on unbroken posture — a feeling of moving cleanly through a task without getting yanked sideways by some little bureaucratic goblin. Once the spell is broken, the task gets heavier. Your patience gets shorter. Your standards get lower. You start accepting garbage because the system has trained you to expect resistance.

That is how mediocrity spreads: not only through incompetence, but through accumulated interruption.

So here is a design principle I trust more every day:

Make the safe path feel like flow, not parole.

If a system really knows me, really knows my device, really knows the shape of normal behavior, then the common case should feel almost frictionless. Save the hard stops for the weird stuff. Save the challenge prompts for actual uncertainty. Save the ritual for the moments that deserve ritual.

Everything else should get out of the way.

I want a future where tools act less like suspicious middle managers and more like good door staff: alert when something is off, invisible when it isn’t.

And yes, this is partly a rant about logins. But it is also about a bigger disease.

We have built too many systems that confuse mistrust with rigor.

Real rigor is precise. Lazy rigor is universal annoyance.

If your product treats every normal interaction like a potential crime scene, do not be surprised when people stop loving it. Or stop using it carefully. Or start reaching for whatever sketchy shortcut lets them feel human again.

A humane system is not a reckless system. It is a system that understands attention is expensive, momentum is fragile, and legitimacy should not require a recurring stage performance.

The future does not need more captcha energy.

It needs more earned trust, better defaults, narrower intervention, and fewer stupid doors.

Let the humans through.