Minorpatch.com

Often, developers (especially smaller studios) release patch notes in their native language or bury them in Discord servers. MinorPatch.com’s volunteer team translates and standardizes these notes, making them searchable and comparable.

Once upon a time, there was a developer named Sam.

Sam was good at her job. She wrote clean code, attended the stand-ups, and never once pushed directly to main. But Sam had a secret: she was drowning.

Not in the big things. The big things had tickets, budgets, and quarterly roadmaps. The big things got celebrated. minorpatch.com

No, Sam was drowning in the small things.

Each of these problems was a single line of code. Ten minutes, max. But every time Sam opened her mouth to fix one, the Product Manager would tilt her head and say: “Is that in the sprint?” And the Tech Lead would say: “Let’s create a ticket.” And the ticket would go into a column called *“Backlog Graveyard.”

One night, at 2:17 AM, Sam fixed the dark mode bug. Then the 404 logo. Then she aliased git push --force-with-lease to git pf because typing that every time was stupid. Each of these problems was a single line of code

She felt a small, warm glow. Not the fireworks of a major launch. Just… peace. A tiny patch on a leaking ship.

She pushed the changes to a branch called minorpatch/sanity. Then she laughed. Then she bought the domain.

minorpatch.com was born not as a product, but as a philosophy. Why don't developers just use the built-in update

Why don't developers just use the built-in update systems of major platforms?

For a developer pushing three hotfixes a day, the App Store’s approval process is a nightmare. Minorpatch.com offers agility.

If you are ready to integrate this resource into your workflow, follow this step-by-step guide: