It Will Break, and That Is Normal
The Feeling Is Part of the Job
At some point the screen will go white, or blank, or fill with red text. Something in your chest will drop. This happens to everyone who has ever built software, including people who have done it for thirty years. The difference is that they have felt it enough times to know it is temporary and almost always fixable. What makes it worse for a first-time builder is a private theory that competent people do not hit this. So a broken screen feels like proof you are not cut out for it. What it actually is, is Tuesday. Naming the feeling helps more than you would expect. It is unpleasant, it is not information about your ability, and it passes.
- Everyone who builds software breaks it constantly — this is the normal state
- Broken is a state to work from, not a verdict on whether you can do this
- The panic is real; it is not evidence of anything
- Nearly everything is recoverable if you kept a working copy
Breaking Is Not the Same as Being Lost
There is a useful distinction between two situations that feel identical. Broken means something specific stopped working, and you can still tell what you changed. Lost means you no longer know what state anything is in, which version was good, or what you have altered since. Broken is a normal working condition and gets fixed in minutes. Lost is genuinely expensive. It is usually the result of many changes made in a row, without checking any of them. Almost every habit in this module exists to keep you in the first situation. Keep copies, change one thing at a time, and check after each change. Those three habits are boring, and they are what separates a bad hour from a lost weekend.
- Broken: one thing stopped and you know what you changed
- Lost: you no longer know which version worked or what you altered
- Every good habit here exists to stop the first from becoming the second
- Copies, one change at a time, check after each — boring and decisive
Take the Thirty Seconds
When something breaks, the strongest move is also the least satisfying. Pause before you type anything. Take thirty seconds to notice what you just changed, what you expected, and what actually happened. That turns a panicked "it's broken, fix it" into a description someone can act on. It also stops the worst reflex, which is firing off three different fixes at once and losing track of which one caused what. If you are genuinely angry, walk away for ten minutes. The problem will be exactly the same when you come back, and you will be better at it. Nobody has ever regretted the pause. Plenty of people have regretted the frantic sequence of changes that followed skipping it.
- Pause and write down what you changed before asking for help
- Never fire off several fixes at once — you lose track of the cause
- Frustration makes you skip exactly the steps that would save time
- Ten minutes away costs nothing and reliably improves your next move
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.