Doing It Again Without Me, and Who to Call When You're Stuck
Okay so. This is the last lesson, and it's a little different from the rest.
We've built the folders. We've named them in plain words. We've got the ten-minute check-in going. Everything up to now has been "here's the thing, let's build it together while I'm standing right here." This lesson is about what happens the first time you hit a snag and I'm not standing right here.
Because you will hit a snag. That's not me being pessimistic, that's just how computers work. Something will look different than it did in class, or a button will have moved, or you'll do a step out of order and get stuck. I want you to have a plan for that moment instead of just closing the laptop and giving up on the whole system.
First, the thing that'll happen to you eventually
I want to tell you about the time I locked myself out of my own account because I was being too careful.
I was updating a password. Good habit, I do it every so often, no complaints there. I typed in the new password, and then — before I actually saved it anywhere — my laptop did an update and restarted itself. Just decided to, mid-task, the way they do. When it came back on, I had a brand new password that existed nowhere except the ten seconds of my brain that had already moved on to something else.
Forty minutes. Forty minutes of account recovery, security questions I hadn't thought about in years, an email to an old address I barely check, the whole mess. All because I changed something before I saved something.
So here's the rule I teach now, and I want you to actually hear this one: save first, then change. If you're updating a password, save the new one in your password manager before you go type it into the actual website. Not after. Before. I know it feels backwards — why would you save a password you haven't used yet — but that ten seconds of "backwards" saves you the forty minutes I lost. Learned that one the hard way so you don't have to.
What to actually do when you're stuck
Here's my honest list, in order, of what to try before you panic:
1. Walk away for five minutes. I know that sounds like a non-answer, but half the time the fix is just coming back with fresh eyes. You'd be amazed how many "I'm completely stuck" moments are actually "I've been staring at this too long" moments.
2. Read the screen out loud, slowly, to yourself. This is the same thing I do when I'm helping someone over the phone — I make them read me exactly what it says, word for word, not what they think it means. Half the time the answer's sitting right there in the error message and we just skipped past it.
3. Search the exact words of the problem. Not "my computer won't work," but the actual error message, in quotes if you can. Somebody else has had your exact problem. Somebody always has.
4. Call the actual company, not a guess. If it's your bank's app acting weird, call your bank. If it's the password manager itself glitching, most of them have a real support chat, and it's usually decent. Don't let a stranger on the internet talk you into anything that involves giving out account numbers or remote access to your computer — that's a real scam pattern, and it's the one caution I'll be a little firm about tonight. A legitimate company will never ask to remote into your machine out of nowhere.
5. Text somebody from class. This is what the group text is for. Somebody in this room has probably already hit your exact snag. That's not cheating, that's the whole point of taking a class instead of watching a video alone.
Where I fall short of "expert," on purpose
I'll say this plainly because I don't want anybody thinking I'm the last word on this stuff: I'm not a security expert. I know password managers, I know two-factor, I know the basics that actually matter for a normal person's normal life. I do not know encryption, I don't know VPNs, I don't get into the deep technical end of any of it. If you ever hit something in that territory — genuinely worried your accounts are compromised, dealing with actual fraud — that's above my paygaid, and I mean that sincerely, go find someone whose whole job is that.
And Mac folks, you know I'm a Windows guy at heart. If you're stuck on something Mac-specific, pair up with another Mac person in the room tonight before we wrap. You'll get further with each other than with me squinting at your screen going "huh, that's not what mine looks like."
The actual goal of all eight weeks
Here's the thing though. I love building these systems. I could set up folders and password managers all day, it's genuinely my favorite kind of puzzle. Keeping it up is the boring part, for me and probably for you too. That's exactly why we built it this way — plain names, few folders, search over sorting, a ten-minute check-in. None of it depends on you being disciplined or clever. It just depends on you doing the small thing regularly, the same way I have to force myself to.
You built this. You did the clicking, you did the naming, you read your own screen back to me more times than I can count. It's yours now. I'm not the one who has to keep it running. You are, and you already have been, for eight weeks. 👍🌞
Before next time: there isn't a next time on the calendar, so instead — save this class's number or email somewhere in your new system (Class stuff, obviously), so future-you knows exactly where to look if a question comes up in six months.