backend engineer · astana, kazakhstan
aitu college graduate · mathematical and computational science undergrad
- ♟️ 2500+ peak on chess.com, bullet mostly. challenges welcome
- 📐 math is the love of my life
- 🎮 making a game. details when it's real
quackiso · rust, duckdb
reads iso 20022 and swift mt bank messages as sql tables — camt statements and
notifications, pacs transfers, pain initiations, and the mt940/mt942 files banks
actually dump. amounts never touch a float, because
0.10 + 0.20 + 0.30 + 1500.10 is 1500.7000000000003 and that is somebody's
money. a 1.7 gb statement parses in about 2 mb of memory, and ci asserts that
number on every push. lives in the
official duckdb community registry;
getting it there involved finding and fixing a bug in the
registry's own release pipeline.
tested against ~280 real messages from more than a dozen banks and vendors; every
special case in the parser is there because one of those files broke it.
moxy · go, redis
a reliability layer for redis queues. a plain pop deletes the task outright, so a
worker that dies mid-task takes it with them and redis keeps no record it existed.
a lease is a claim with an expiry, so an unacknowledged task comes back instead.
the lease is journalled before anyone can see it, and a restart replays the
journal rather than stranding what was in flight. every crash window is
enumerated in docs/failure-matrix.md with the test that proves it; the
guarantee is at-least-once, not exactly-once.
chessview · python, typescript
realtime chess where the server owns the board and every clock, and the client gets no vote. clients send intent and are told what happened. disconnects pause the clock instead of losing the game, and engine analysis runs in your own browser rather than on my bill.
everything else
- search-gateway · python — one gateway over five search apis; every failure is blamed on the key, the provider or the caller before anything decides whether a retry is the right move
- db-seed · go — seeds a database in dependency order; the sort runs twenty times in ci, because one green pass does not distinguish a correct ordering from a lucky one
- shipwatch · python — release tags and iso 20022 changes become github issues and telegram messages, on their own
- jot · javascript — telegram bot that keeps notes as github issues; anything you send is a note,
/taskpromotes one later - bugchat · python — a telegram bug chat becomes a plane board; bursts from one author become one task instead of three fragments
- mentor-skill — an agent skill that refuses to let you merge code you can't explain
- terminal-setup · powershell — one script, and the beige is gone
