Patch

You fixed the bug. Now you have to get that fix out to everyone using the thing, without rebuilding the whole product or making them reinstall from scratch. The small, targeted fix you send out is a patch.

A patch is a small update that changes part of existing software to fix a problem or close a hole, without replacing the whole thing. The word is literal. Like a patch sewn over a tear in jeans or glued over a hole in a bike tire, you're not buying new jeans or a new tire. You're mending the one bad spot and leaving the rest alone.

That "leave the rest alone" part is the whole appeal. A program might be hundreds of thousands of instructions. When one of them is wrong, you don't want to rewrite the program, you want to change that one piece and ship just that. A patch is a small change that fixes the problem, which makes it fast to make, fast to review, and less likely to break something else along the way.

You meet patches constantly without the name. A "security patch" on your phone is exactly this: a small fix sewn over a specific hole, usually one attackers found. When you hear a company "patched the vulnerability," they didn't rebuild the app, they stitched over the one weak spot, fast, because the hole was dangerous left open. A "hotfix" is just a patch shipped in a hurry because something's actively on fire.

A couple of connections so it sits in the bigger picture. Shipping a patch still means you deploy, push the change live, so a patch is often what you're deploying, the content of the update. And if a patch itself turns out to make things worse, that's exactly when you reach for a rollback, snap back to the version before the patch while you sort it out. Patch forward when you've got the fix. Roll back when you don't yet.

Why a non-coder should care: it right-sizes the ask. When something's broken and you (or your AI) "just need to patch it," that's not a big scary rebuild. It's the surgical version: find the one bad spot, mend it, ship that. A lot of real work in software is exactly this, small patches one after another, each closing one hole. Not dramatic. Just steady mending.

A patch is a small fix sewn over one bad spot in software, not a whole new garment. Find the hole, stitch it, ship just that. It's most of how software actually gets better over time.