Challenge Sprint + Debugging Championship

Create debugging challenges (June 15-30) or compete to solve them (July 1-7). Certificates and badges for all participants.

View now

Open source, free forever

Stop grinding LeetCode.
Start fixing real bugs.

Most coding platforms test if you can reverse a linked list. Nobody cares. What actually matters is tracing a null pointer through 12 files at 2am.

Star on GitHub Sponsor

1Traceback (most recent call last):
2  File "app/handlers/message.py", line 47
3    in process_message
4  File "app/services/queue.py", line 23
5    in enqueue
6TypeError: 'NoneType' object is not subscriptable
7 
8Context: user_id=4521, channel="general"
9Last successful: 2 minutes ago
10Failure rate: 23% of requests

Start here. What is the actual problem?

The workflow

Clone. Fix. Submit.

Everything runs locally. Clone the challenge repo, fix the code, submit when you are done. No browser IDE. No hand-holding.

recticode startrecticode submit

terminal

$recticode start ghost-payments

Get started

Install and go

One install, no accounts, no setup wizard. Just pip install and start debugging.

# Install

pip install recticode

# Login with GitHub to retain progress

recticode login

# See all challenges

recticode list-challenges

# Start a challenge

recticode start [challenge_name]

# Submit your fix

recticode submit

# All commands

recticode --help

Current challenges

Real bugs from real codebases

Mediumpython / sql

Ghost Payments

Orders are being marked as paid even when the payment fails. This seems to happen inconsistently.

Hardpython / json

Job Queue

This job queue allows multiple workers to process the same job at the same time due to a race condition.

Easypython / sql

Ratelimiter

This ratelimiter seems to never be ratelimiting people.

Community driven

Create your own challenge

Got a gnarly bug you solved at work? Turn it into a challenge for others to learn from. Submit your repo and we will review it for inclusion.

Read the submission guide

How it works

Debug like you would at work

Read the stack trace

No hints. Start where every real debugging session starts: an error message and a pile of code.

Trace the issue

Navigate across files. Understand the codebase. Find where things broke and why.

Write the fix

Actual working code that passes the tests. The kind you would push to main.

Built in the open

recticode is open source and free forever. Follow the repo to get notified when we launch new challenges and features.

Follow on GitHub Sponsor this project