Solving "Coding Atrophy" caused by AI - Battledevs

Kinetikus — Thu, 10 Sep 2026 23:39:33 +0000

Completing a prompt is not the same as solving under a fuse

You already know the feeling. The model writes. You skim. You merge. A week later you cannot rebuild the same function without opening the chat again.

That is coding atrophy. Not “AI is bad.” You stopped doing the reps.

Battledevs is the gym for that. A realtime player-vs-player coding pit: LeetCode-style problems, a live Python judge, a clock, and another human on the other seat. You write the solution. Tests score as you send them. First to the room goal wins.

The game is how you stick with it.

What Battledevs is

Battledevs is a live coding arena, not a homework site you abandon after two nights.

Python only — one language, one editor, no setup theater.
Live judging — submit and isolated workers run your tests in seconds. You see cases pass or fail while the fuse is still ticking.
Same problem set, same clock — you and your opponent load the same tickets. No silent autocomplete duel.
Score, not vibes — Easy / Medium / Hard tests pay 5 / 10 / 15 points. First player to the room goal takes the pit.

The landing even lets you type in a real Monaco editor before you sign up. No submit on the homepage — just the feel of the keys.

Why it exists

AI made shipping faster and practice optional. Optional practice dies.

We built a pit where:

You sit across a human at your rank.
You load the same problems.
You submit Python with your own hands.
You score — bits move, hats climb, you want another set.

Four beats. Then your hands remember.

The problems

These are algorithm tickets, not trivia.

Each problem is a real-life scenario wrapping a classic pattern — arrays, hash tables, two pointers, graphs, DP — written as CommonMark you actually read. Titles sound like a place and a job, not TwoSum_v3. Examples and constraints sit in the prompt. Hidden tests are story-world data, not [1, 2, 3] clones of the sample.

A ranked match deals three problems. Difficulty is not a coin flip: rarity follows the hats at the table, so a yellow-hat pit is not the same hand as a black-hat pit. You will not see the same tickets you just played in your last two games.

In the pit you get:

A problem bay (prompt is not copy-paste bait)
A Python editor with Reset / Revert
A case tape — Run to probe, Submit to score the room

The homepage sample, Call Sign Pair, is the shape: easy hash-table thinking, a story, two examples, tight constraints. Catalog problems go harder. Settings rotate so you are not solving “warehouse inventory” forever.

You are practicing writing, not prompting a walkthrough.

Five ways to take the reps

Ranked — the daily gym

1v1. Match by hat. Race three problems. Take bits when the code actually lands.

After a minute of waiting you can widen search to the next hat up so the queue does not stall. This is the default workout.

Custom — the friend pit

Host a room. Share the id. 2–6 seats, same live judge, same clock. Spectate is a thing for public custom and tournament pits if you want a gallery, not a second keyboard.

Solo — the quiet set

No opponent. Same editor, same problems, same submit path. Use it when you want the tickets without a race.

Tournament — make the practice a night

Single-elimination cups for 8, 16, or 32 players. Live rounds, standings, match resume, a champion on the tree.

Anyone can join. Hosting a cup is a paid-pass unlock. You can set a bit gate from earned play status — bits are not for sale. The arena is one floor: brief, bracket, signed list, previous pits.

A cup is still a workout. It is also loud.

Interview — see them write, not paste

Host a live session. Shared Python editor, a system-design board, one clock, the same judge as a match.

You start when both seats are in. You watch keystrokes, not a pasted essay. Problem ticks show which ticket each candidate has open.

The game layer (so you come back)

Passing tests scores the room. Winning ranked climbs a hat ladder. Ten stations, bit thresholds, a public leaderboard.

That is not cosmetics. It is why a Tuesday night ranked set beats “I’ll do LeetCode later.”

Scoring is honest and small:

Difficulty	Points per passing test
Easy	5
Medium	10
Hard	15

First to the goal wins. The fuse is the workout.

What you will not find

A dozen languages on day one. Python.
A judge that waits until the round ends. Results land while you are still typing.
Problems that exist only as function signatures with no world. Ours arrive as scenes.
Bits you can buy. You play for them.

Start the cure

battledevs.com — create a seat, enter the lobby, queue a human.

Write it yourself. Watch the tests. Enjoy getting the skill back.

Tired of paying for Burpsuite so I started SNORPY

Kinetikus — Sun, 28 Jun 2026 20:40:52 +0000

Disclaimer: Snorpy is for authorized security testing only. Use it on systems you own or have explicit permission to test.

Why I started building this

Burp Suite is excellent. I’ve used it, I respect it, and for serious engagements it’s still the benchmark.

But between licensing costs and a stack I couldn’t easily extend, I kept thinking: what if there was an open-source alternative built with the tools I already use every day — React, TypeScript, Electron?

That’s why I started Snorpy: a desktop MITM proxy with Proxy, Repeater, and Intruder. It’s early, it’s Apache 2.0, and it’s open for contributors — not a Burp clone yet, but a project I wish existed when I started pentesting.

Important honesty up front: Snorpy is not a full Burp replacement yet. Proxy, Repeater, and Intruder work today. Spider, Decoder, Comparer, and more are on the roadmap. I'm sharing this now because I'd rather build it with feedback than polish in private forever.

What Snorpy does today

✅ Working now

Tool	What it does
Proxy	HTTP(S) intercept on port `8080`, target scoping, request hold/modify/forward
Repeater	Edit headers/body and resend requests manually
Intruder	Fuzz with `§placeholder§` markers, wordlists, configurable concurrency

🚧 Coming soon

The sidebar already sketches the roadmap: Spider, Decoder, Comparer, Buster, AI Analyzer, log export, and project settings. These are great places to contribute if you're looking for a first PR.

Architecture: why Electron + mockttp?

Snorpy splits cleanly into two worlds:

DEV Community: Kinetikus