In 1928, Alexander Fleming went on vacation and left a stack of petri dishes unwashed in his lab. When he came back, one dish had gone moldy — contaminated, ruined, exactly the kind of thing most bacteriologists would toss without a second look.

Fleming looked anyway.

Around the mold, the bacteria he'd been growing had died. Something in that contamination was killing them. Most scientists in his position would have seen a failed experiment. Fleming saw a question worth chasing — and that question became penicillin, the discovery that would go on to save more human lives than perhaps any single invention in history.

Here's the part of the story that gets skipped: Fleming wasn't the only bacteriologist whose dishes got contaminated that summer. He was almost certainly not even the first. What made the difference wasn't the accident — it was that he was one of the rare people willing to stop and ask "wait, why did that happen?" instead of just cleaning up the mess and starting over.

The actual lesson isn't "sometimes messy accidents lead to great discoveries." It's narrower and more useful than that: the anomaly you're tempted to just clean up and ignore is often more interesting than the result you were originally looking for. Most of us are trained to treat "that's weird, let me just redo it properly" as the responsible move. Fleming's whole career pivoted on doing the opposite — on treating "that's weird" as the actual signal worth following.

Next time something in your own work comes back wrong — a number that doesn't add up, a result that shouldn't be possible — it's worth asking whether you're looking at a mistake to clean up, or a Fleming moment you're about to talk yourself out of.