ALAN BAGEL

2D roguelike where runs escalate through denser waves and tighter resource windows. I spent most of my time on two things: making combat feel responsive (clear telegraphs, tight hit feedback) and keeping frame pacing stable when there are 50+ entities on screen.

• * enemy waves, bosses, and upgrade runs built from scratch
• * combat tuned around clear telegraphs and sharp hit feedback
• * stable frame pacing with 50+ active entities on screen
• * custom AI and balance work for late-run difficulty scaling

ACSL competition prep platform I built to teach students at my school. The existing study resources were scattered across random PDFs and forum posts, and none of them tracked what you'd actually learned. Used by 10+ students for contest prep.

• * 30+ lessons across all four contest categories
• * timed practice sets that mirror real contest format
• * per-account progress tracking with Supabase auth
• * mixed quiz mode pulling from every topic at random

Write Python-like syntax, get C++17 out. I built this because writing C++ under contest pressure is mostly fighting syntax. The compiler only emits the stdlib functions your code actually uses, so the output is short enough to submit directly.

• * Python-like syntax that compiles down to contest-ready C++17
• * output only includes stdlib helpers your program actually uses
• * designed to cut syntax friction when speed matters most
• * compiler/runtime work split between Scala 3 and C++17