Isroil Baxtiyorov

Exhibits

What it was before

The staff review system was broken and personal roles were issued by hand — with roughly 200 tickets a day, all of it landed on the administration team.

What was built

• Staff performance review

  Rebuilt from scratch after the previous implementation failed, including moderator work quotas.

• AI staff member in tickets

  Answers from a knowledge base, escalates to humans, and closes a ticket after inactivity. DeepSeek V4 Flash.

• Personal roles

  Previously issued by hand. Now self-service: granting, in-place editing, and delegated rights.

• Clan system

  Creation, membership, tasks, shop, wars, and progression.

• Tickets

  Support, complaints, suggestions, clan applications, and donation roles.

• Moderation

  Mutes, bans, kicks, and appeals.

• Nightly export loops

  Statistics collected at 23:55 and online figures exported to Google Sheets at 23:57. No human in the loop.

Outcome

The senior administration team's workload dropped substantially: triage is automated, roles are issued without manual work, and the daily logs write themselves.

Exhibits

What it was before

The project and its community were built from nothing, and in game communities “write me in DMs” is a standard opening move for a scammer.

What was built

• Scam-pattern detection

  Public messages are scanned for DM-solicitation patterns, and the warning goes to the recipient rather than only to staff — the person actually at risk is the one who hears about it.

• Tickets

  Support, complaints, and suggestions with staff review.

• Moderation

  Mutes, bans, kicks, and appeals.

• Nightly export loops

  The same scheme as ReallyWorld: statistics and online figures go to Google Sheets on a schedule.

Outcome

Not filled in

What was built

• A schema that survives its own changes

  SQLite with its own column check: the database extends itself in place, and data already written stays where it is.

• A control panel in the browser

  A separate web panel beside the bot, where the state updates itself without reloading the page.

• Tests, actually present

  A test suite lives in the repository — not planned, but written and kept alongside the code.

• One owner, not a public bot

  The bot answers a single owner by id — a privacy decision, not an unfinished feature.

Outcome

A personal assistant in daily use: the database extended itself in place through five versions without losing a single written note, and the tests live beside the code.

What was built

• Deploys itself

  A push to the repository builds the image and rolls the bot out to fly.io with no manual step: the Docker image, the machine configuration and the workflow all live beside the code.

• Adding an entrance, step by step

  A six-step dialogue — quarter, house, entrance, floors and apartment range — instead of one form that is easy to get wrong.

• Reviewing requests

  Requests are approved or rejected by hand, and payment history is available as its own command.

• Every button in two languages

  Russian and Uzbek are built into the buttons themselves rather than translated over the top — in Tashkent that is not optional.

Outcome

Deploys with one push: a fresh image is built and rolled out to fly.io with no manual step, and both language buttons work out of the box.

Exhibits

What was built

• A browser only when there is no other way

  Plain requests first, with a headless browser started only when protection is detected — it costs far more, so it runs when it must rather than by default.

• Ranked by price against quality

  Each listing's price is scored against the median of the result set, then defects found in the description are subtracted by severity — cosmetic through blocking. The total opens up line by line, so you can see what it is made of.

• The search reports as it runs

  A long scrape streams its progress into the interface, instead of an empty screen with a spinner on it.

• Three languages and a dark theme

  The interface is in Russian, Uzbek and English — the same three languages as this page.

• A database you can swap

  A SQLite file by default, switched to Postgres by configuration — easy to start, and able to grow without a rewrite.

Outcome

Finds and ranks listings on its own scale: prices scored against the median, defects subtracted by weight, and the scrape's progress streamed into the interface.

What was built

• Wake-on-LAN

  `/wake` sends the magic packet; `/wakewait` waits until the agent on the machine is actually online.

• Sleep, hibernate, shut down

  Separate command paths for Windows and for Linux, rather than one written for a single system.

• Host status

  `/status` and `/health` report whether the machine is reachable and what the agent says.

• Two processes, not one

  The bot and the agent on the controlled machine are separate programs, so the bot stays reachable while the machine is off.

Outcome

Runs daily on the owner's machine: control commands flow through the two-process design, and the machine's state is visible without standing in front of it.

Exhibits

What was built

• The data lives on the device

  IndexedDB via Dexie: five schema versions, three of them migrating notes already saved — the structure changed underneath live data and the data survived it.

• Installs as an app

  A PWA with auto-update that works offline and accepts links shared from other apps.

• Voice capture

  Speech transcribed on the device itself through the Web Speech API, with no audio leaving it.

• A graph of links

  Notes mature through stages and link to one another; the links are visible on their own map.

• Sync across devices

  Supabase with magic-link sign-in — no password, because there is none to lose.

Outcome

A living notebook on every device the owner owns: five schema changes survived by the data already written, sign-in by a link from email, and no audio ever leaving the device.