What "It Works on My Machine" Hides
Your Machine Is Not Neutral
Your computer is a specific environment, carrying a great deal of invisible help. Files sitting in a folder that will not exist elsewhere. Settings you configured weeks ago and forgot. A browser already signed in. A fast, stable network. Data left over from testing that makes the app look populated. None of this travels with the code. So an app that works perfectly for you can fail immediately for the first other person — not because something broke, but because the invisible scaffolding was never part of what you shipped. This is one of the oldest problems in software and it catches everyone. The point is to expect it, rather than to be surprised by it.
- Local files, settings, sign-ins and test data are invisible and do not travel
- Working locally is evidence about your machine, not about your app
- A fresh visitor gets none of your accumulated scaffolding
- Expect this rather than treating it as something breaking
Test It Like a Stranger
Before you share anything, use it the way a stranger will. Open the live link, not your local version. Use a different browser, or a private window, so you are not signed in and have no saved data. Use a phone on mobile data rather than your home network. Create a brand new account if there is one. Then walk your entire checklist in that state. This takes ten minutes and finds the majority of "it worked for me" failures: the sign-in that only worked because you were already signed in, the page that only loaded because the file was on your desktop, the flow that assumed data you had created last Tuesday.
- Use the live link in a private window, signed out, with no saved data
- Try it on a phone on mobile data, not your own network
- Create a fresh account and walk the whole checklist as that person
- Ten minutes here finds most works-for-me failures
The First Five Minutes After Sharing
When you do share it, watch. Keep the link open, keep the service dashboards visible, and check for errors as the first people arrive. The first few real users find things nobody predicted. The difference between a small problem and a bad story is usually whether you noticed within minutes or the next morning. Have a way to take it down quickly. Know in advance how to disable the link or put up a holding message, because being able to stop is more valuable than being able to fix under pressure. Share with a handful of forgiving people first, and widen it only once that group has been through without incident.
- Watch the first arrivals rather than sharing and walking away
- Know in advance how to take it offline quickly
- Start with a few forgiving people, then widen
- Noticing within minutes is what separates a hiccup from a story
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.