Handling mistakes as a web developer
One thing I like about web work is how often a mistake is recoverable. Bad change? Undo, revert the commit, push again. You can still burn time, upset a client, or lose data. Recovery is usually on the table.
Doctors, structural engineers, and pilots live with a different failure cost. People can die when they get it wrong. That does not shrink our craft. It does change the kind of pressure we carry day to day.
Easy reverts can still make me sloppy. I have skipped care because “I can fix it later,” and that habit bites. The safety net is useful. It is a poor excuse for skipping the boring checks.
I look back at old screw-ups now and then. The point is the lesson, not self-punishment. Reverting a broken deploy at 2am still sucks. Getting it right on the first try still feels better when I can.