what I am building
Work
What I am building now, and the products I spent years on before that.
earworm.school
English through rock and metal songs, for Russian speakers. You pick a band, then a song, and either just listen or start the exercise. Each line plays on its own, and you put it back together from shuffled words. A wrong word won't go in, and after three misses the right one lights up. Once the line is built, you see its translation. The interface is in Russian and English, and I add bands, songs, lines and translations through an admin panel of my own.
- React 19
- Vite
- Hono
- Bun
- PostgreSQL
- Cloudflare R2
- k3s
ogarich89.com
This site, as it happens. React with server-side rendering, a design system of my own built on tokens, and a separate API. The server and the infrastructure are mine too. The project is right in front of you: it is what you are reading.
- React 19
- Fastify
- Hono
- Bun
- k3s
Back office admin panel
An internal panel the office works in every day, built with React and react-admin. I did not write it from scratch. I am gradually putting it in order: updating the stack, clearing out old and dead code, improving CI/CD, and dealing with the screens that used to be visibly slow.
- React
- react-admin
Landing generator: a page is a domain
A landing page generator on Next.js, where every page can live on a domain of its own. There is one codebase behind them and no limit on how many sites it serves. Launching one more landing page no longer means standing up a whole new project.
- Next.js
quantpilot.com
A startup we began from nothing together with the 3Commas team. I put the monorepo together and worked out the architecture: the API on Nest.js and Prisma, the frontend on Vite. After that I set up the whole path from a commit to production, took part in choosing the technology, and built the AI side: skills, agents and the tools they use.
- TypeScript
- Next.js
- Nest.js
- Prisma
- Vite
- Bun
3commas.io
A crypto trading platform and almost five years of my life. I owned the public side on Next.js and Prismic, and took part in the big move of the frontend out of a Ruby on Rails monolith into a separate SPA. It ran on Webpack at first and moved to Rspack later. Over those years I worked on nearly everything around the frontend: architecture and rendering, bundle size and load speed, CSP and security headers, CI/CD and Kubernetes. I wrote our own lint rules and set up Sentry and test coverage. API client types were generated from Swagger, and translations went through Crowdin.
- React
- Next.js
- TypeScript
- Rspack
- Prismic
- Kubernetes
VTB Digital Banking
The client side of a digital bank. The frontend was split into a root, a platform and namespaces, which were separate parts of the application. Shared libraries were built once through the Webpack DllPlugin, and later the whole arrangement moved across to microfrontends. I worked on the architecture, on adaptive and cross-browser layout, wrote Webpack plugins of my own, and worked on Storybook for the component library.
- Webpack
- Babel
- Storybook
- Microfrontends
Pizza Mafia
Pizza delivery, and another project on the same approach. One application ran on both the client and the server. I worked on the build, on load speed and on adaptive layout.
- React
- Koa
- Webpack
Сакура
Another delivery project from those same years and on the same stack. One React application rendered on both the client and the server, built with Webpack and Babel. I worked on load speed and on adaptive, cross-browser layout, so the site held up not only in modern browsers but in whatever people were actually using.
- React
- Koa
- Webpack
Суши Wok
A food delivery chain and one of my first large SPA projects. Client and server were written in React and Koa, with rendering on the server. I worked on the build with Webpack and Babel, on load speed, on adaptive and cross-browser layout, and on code review.
- React
- Koa
- Webpack