Change your password for "security"
Forced resets don't fix bad habits. Ten minutes sat next to someone does.
On this page
Story time...
There's a particularly antiquated company I deal with at work, which shall remain nameless, and they have what I call the Goldilocks rule. Your password can't be too short and it can't be too long, and you can only use certain special characters. Which ones? You'll find out if you got it right when you press enter, so you'd better temporarily copy and paste that password somewhere you can make all the little tweaks that are needed to satisfy their stupid system. All I want is to log in, change something and get out again. Who did I offend to deserve this kind of treatment? Hopefully they can forgive me.
I was under the impression that outside of this one company I wouldn’t have to deal with it again, but the offence must have been quite strong, because on a random Wednesday evening, minding my business, about to log in to a website, I got greeted with:
Your password was last changed 155 days ago on the 2nd June, 2026. We recommend you update your password regularly.
I might have mistaken it for sage advice if it weren't for the fact that it's been bad advice for years. NIST and the NCSC both say not to force regular password changes unless there's a sign of compromise. The policy hangs around anyway, because it looks like security, and a tick-box exercise is like catnip for corporations.
Oh, and the icing on the cake: they don't even have MFA.
I then spent the next three hours putting this together, but I can’t pass up a good opportunity for a rant.
Password, please.
OK so, here's the problem. Most people aren't using a password manager out of choice. Take my dad. He uses the one built into his browser, so on paper he's doing the right thing. Is he still reusing the same few passwords everywhere? You bet he is. And I'm not entirely sure I'm brave enough to show him what a proper password manager can do. When a system forces him to change his password, he'll tweak the one he already has, add a number, swap a letter for a symbol, and carry on. Now multiply that by every user in an organisation, and then around the world, and you've got a policy that annoys everyone and protects very little.
I already use a dedicated password manager (actually, I have three, but who's counting?). Each and every account has its own long, random password in varying lengths. I think the longest I've done is 127 characters. Whyyy? Who cares? I don't have to remember it, so it doesn't matter. The rotation is just performative, like acting on stage, except this time the acting is bad and I want my money and time back. The old password is just as secure as the new one. The only difference is you've wasted my time with your need to play pretend. A 127-character random string doesn't go stale because the calendar says so.
Nobody ever showed them.
But the part that stayed with me isn't the policy. It's the people.
On the day of writing this, I helped someone set up a password manager earlier in the afternoon. She'd been keeping her passwords in a notes app on her phone. The look on her face when it clicked, when she saw how much easier it made things, was priceless. It made my day. Last month I did the same for someone I used to work with, while we were catching up in a bar. I found it interesting that they both keep their passwords in a notes app, and neither of them trusts the in-browser managers.
You know what? I found that refreshing, actually. A bit of wariness about big tech is healthy, and I've had my own reasons lately to agree. I'm late to the party, but better late than never.
What struck me is that neither of them was careless. They had good instincts and nobody had ever shown them a better option. A notes app beats reusing passwords, but it isn't built for the job, and a dedicated manager is. All it took was someone sitting next to them for ten minutes.
That's the gap I keep seeing in IT. We write policies telling people what to do, and we skip the bit where we show them how. And let's not forget the why.
Gather around.
On the corporate side, you need to do better and stop reaching for the low-hanging “change your password” fruit. Build more robust systems. Push for MFA or passkeys, and favour length over complexity rules (the three random words approach comes to mind, and it’s effective). Check against known breached passwords, and only ask for a password change when there’s a reason to, not because the timer ran out.
On a personal note, if you too have someone in your life who has to go digging for their password every time they see a login page, pull up a chair and help them get set up with a password manager. It will look impossibly confusing at first, but they will realize it’s just like their notes app, except it’s doing a lot more to protect them than they know. Just make sure they choose a completely new password for it, one they’ve never used anywhere else. And you’ll probably get the same look I did.
Related Mo'ments

Earlier sunsets, a 144-day fight to get my Microsoft account back, a charity website migration that turned out bigger than expected, a homelab with a new dashboard and a smarter location history, and a rebuilt blog editor. Soundtracked by Woodkid and BØRNS.

September: a third London to Brighton ride (the slow one), Arcadia with a seat this time, a NAS that went from 8GB to 64GB, and a record 21 films, plus the usual theatre, books, and music.

August brought a Kintsugi lesson in breaking things on purpose, a NAS that has finally gone quiet in a good way, a self-indulgent movie marathon, a genuinely dazzling magic show, and more Dungeon Crawler Carl chaos.