We Planted 180 Bugs in Copies of Real Open-Source Backends. Fix Your First One in About 20 Minutes
PushForces is a free, early‑alpha platform that gives developers real backend code from open‑source projects and plants bugs for them to fix. Each task, called a ticket, ranges from a simple TODO to a full incident report, and is judged by hidden tests that mimic production checks. The site offers…
PushForces is a new practice site that lets developers sharpen the exact skill most teams need: finding and fixing a reported bug in someone else’s backend code. Unlike algorithm platforms that give a single function to write, PushForces hands you a slice of a real open‑source project, plants a bug, and then runs hidden tests to verify your fix.
What the Platform Looks Like
Each task is called a ticket and comes from one of 27 well‑known open‑source backends, such as Formance Ledger for money tracking, Ory Kratos for authentication, and Navidrome for music streaming. The tickets are graded on a 1‑star to 5‑star scale. One‑star tickets are simple browser exercises that highlight a TODO comment. Five‑star tickets are full incident reports that require a private git clone, a branch, a push, and a 2‑hour or longer turnaround.
All tickets are free. The first 93, labeled 1‑ to 2‑star, run entirely in the browser using the Monaco editor (the same code editor that powers VS Code). No account is needed for these warm‑up exercises. For 3‑star and higher tickets, you must sign in with an email, Google, or GitHub account to receive a unique git token and a private remote. The platform then runs your push in a disposable container that mimics a production environment.
How a Ticket Works
When you accept a ticket, the system gives you a copy of the relevant repository files. For easy tickets, the copy contains a single editable file with a TODO marker. The goal is to replace the TODO with correct code and submit. For harder tickets, you clone the private repository, create a feature branch, reproduce the bug locally using the provided smoke tests, fix the code, and push your changes. The CI system then runs three layers of tests: public smoke tests, hidden tests that were never shown to you, and an integrity check. Only if all three pass does the ticket get marked “Accepted” and you earn experience points.
The hidden tests are crucial. They reflect real production failures—null pointer dereferences, race conditions, and incorrect calculations—that the platform deliberately planted. Because you never see them, you must understand the code, read the bug report, and deduce the correct behavior, just as you would when responding to a support ticket in a real job.
Why PushForces Is Different
Most coding practice sites focus on algorithm puzzles or building something from scratch. PushForces is the first to combine three industry staples: real code, a git workflow, and hidden tests. It also mirrors the incident‑driven nature of many backend teams, where a bug report arrives with a severity level and a service‑level agreement (SLA). Some five‑star tickets even carry a SEV1 label with a 120‑minute deadline, adding urgency and realism.
Because the platform uses actual open‑source projects, developers get to see how mature codebases are structured, how types are defined, and how conventions are applied. The warm‑up tickets teach you to navigate unfamiliar code quickly, while the harder tickets force you to reproduce failures, read logs, and write a fix that passes unseen tests.
Getting Started and What Happens Next
To try a 1‑star ticket, simply click the “Run” button after editing the TODO. A quick smoke test will run locally, and if you hit the “Submit for CI” button, the platform will run the full hidden suite. For a 3‑star ticket, you’ll need to clone the repo, create a branch, and push your changes. The platform limits each account to ten judged pushes per 24‑hour window for 4‑star and 5‑star tickets, but 1‑ to 3‑star tickets are unlimited.
Once you submit, the CI container runs. If your fix passes, the ticket is marked accepted, you earn experience points, and the platform updates your profile with your success rate. If it fails, you can read the failure report, fix the code, and try again—no penalty or cost.
PushForces is still in alpha, but the team behind it has no plans to charge. It is open to everyone and aims to fill the gap between algorithm practice and the real debugging work that most developers do on their first day on the job.
Where It Stands in the Landscape
When compared to sites like LeetCode, Exercism, CodeCrafters, SadServers, and Buglyst, PushForces uniquely offers real‑world code, a git workflow, and hidden tests. Buglyst also uses hidden tests but mostly provides custom labs; PushForces pulls from 27 real projects. The platform’s focus on incident‑style tickets and realistic deadlines sets it apart from the more generic coding challenges found elsewhere.
For developers looking to transition from algorithm practice to real backend work, PushForces offers a hands‑on, realistic environment that mirrors the day‑to‑day tasks of a software engineer.
Conclusion
PushForces is a free, browser‑based practice platform that gives developers a taste of real backend debugging. By working on real open‑source code, following a git workflow, and passing hidden tests, users can build the exact skills needed for a production engineering role. The platform’s early alpha status and zero‑cost model make it an attractive option for anyone wanting to bridge the gap between coding interviews and real‑world software development.
Why it matters
Real‑world debugging is the daily reality for most developers, yet few platforms replicate that environment. PushForces fills this gap, helping engineers transition smoothly from interview puzzles to production code.
Key points
- PushForces offers free, real‑backend debugging practice with hidden tests.
- Tickets range from simple TODO fixes to full incident reports with SLAs.
- Harder tickets use a git workflow and private repos, mirroring real teams.
- The platform uses 27 open‑source projects, giving authentic codebases.
- It combines real code, git, and hidden tests—unique among practice sites.
Frequently asked questions
Do I need to install anything to use PushForces?
No. The first 93 tickets run entirely in your browser. Harder tickets require only a git client and a text editor, no special setup.
Is there a cost to use PushForces?
PushForces is free now and has no announced plans to charge. All tickets are available at no cost.
What happens if my push fails the hidden tests?
You can read the failure report, fix the code, and submit again. There is no penalty or cost for failed attempts.
Can I use PushForces to prepare for a job interview?
Yes. The platform trains the exact skill of finding and fixing bugs in existing code, which is common in many interview and on‑the‑job scenarios.
.jpg?w=1120&h=630)
