¿Puedo vibecodear LeetCode?

NO TANTO · sigue valiendo pagarlo

precio $35/mesahorrarías $420/añotiempo de build un fin de semanacategoría 💼 carrerareemplazada por 0 personas

An agent can produce a Monaco editor, a problem list, a submissions table and a Judge0 sandbox in a session, and none of that is the product. LeetCode is a content and coordination asset: thousands of curated problems with hidden test cases that actually catch off-by-one and TLE, editorials, company frequency tags, and the social fact that interviewers pull questions from it, which you cannot self-host. Clone the harness and you sit staring at an empty problems directory; authoring good problems with adversarial test cases is the actual job. Build the trainer if you want a private drill rig over problems you have already seen, but do not pretend it replaces the bank.

el prompt

Build a local coding interview trainer. One repo, single user, no accounts, no cloud, no telemetry. It runs on my machine.

Stack, not negotiable: Python 3.11 with FastAPI on the backend, SQLite through SQLAlchemy, a Vite + React + TypeScript frontend using the Monaco editor, Docker for code execution. Do not add auth. Do not add a hosted judge API.

Problems live on disk, not in the database. Each problem is a folder under ./problems/<slug>/ containing problem.md (the statement), meta.yaml (title, difficulty, topic tags, language stubs) and tests.json (an array of {input, expected} objects, including at least one large case for timing). Write 12 seed problems yourself covering arrays, two pointers, a stack, binary search, BFS on a grid, interval merging, and one small DP. Do not scrape or reproduce LeetCode content.

Execution: POST /api/run accepts {slug, language, code} and runs it in a throwaway Docker container. Only python:3.11-slim and node:20-slim images. Flags: --network none, --memory 256m, --cpus 0.5, --pids-limit 64, read-only root filesystem, non-root user, 5 second wall clock kill. Wrap the submitted function with a harness that feeds each test case and compares output. Return per-test pass or fail, stderr, and runtime in milliseconds. Never execute submitted code outside Docker, not even in dev mode, not even as a fallback.

Store every submission in SQLite: slug, language, code, verdict, runtime, timestamp. I want to diff my third attempt against my first.

Review queue: SM-2 style spaced repetition over solved problems. Correct solve pushes the next due date out, a failure resets it. GET /api/due feeds a Today view that tells me what to redo.

UI, three routes: problem list with difficulty, last verdict and next due date · problem view with statement left, Monaco right, Ctrl+Enter to run, results panel below · stats page with a solve calendar and per-topic pass rate.

Explicitly out of scope: contests, leaderboards, other people's solutions, discussion threads, company tags, languages beyond Python and JavaScript, mobile layout, deployment.

Ship a README with a single make dev command and a .env holding only PORT and DOCKER_HOST. Before you claim it works, prove the sandbox survives an infinite loop, a fork bomb, a 2 GB allocation, and an outbound HTTP request, and paste the output.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

por qué la gente sigue pagando

Because thirty-five dollars for the month before an onsite is trivially cheap against the salary delta, and because nobody wants to author their own curriculum while also preparing for interviews. Premium buys company-filtered lists and editorials, which is a shortcut through the one resource candidates are actually short on: time. A self-hosted drill app competes on none of that. It competes on being a nicer place to redo problems you already understand, which is a real but much smaller need.

qué pierdes

xEl banco de problemas en sí, miles de problemas con pruebas ocultas ajustadas para detectar las formas específicas en que la gente se equivoca

xEtiquetas por empresa y datos de frecuencia, que es la razón principal por la que la gente paga Premium

xEditoriales y los hilos de discusión donde ocurre el aprendizaje real

xConcursos, calificaciones y la leve humillación pública que hace que sigas volviendo

xCualquier señal de que estás practicando las mismas preguntas que te hará tu entrevistador

arte previo · úsalo en vez de construir, si prefieres

Nada que valga la pena señalar. Por eso existe el prompt.

compartir en X ↗"Acabo de reemplazar LeetCode ($35/mes) con un prompt"