tabrez.dev

Developer · Tech lead at PinShop TJ

I turn problems intoproducts that work

I'm Tabrez Shonizorov — a hands-on developer and the technical lead of PinShop TJ. I design solutions, set up the development process and own the result.

FollowGet in touch

Working with

TypeScriptTypeScriptJavaScriptJavaScriptReactReactNext.jsNext.jsAngularAngularReduxReduxReact QueryTanStack QueryTailwind CSSTailwind CSSSassSassViteViteWebpackWebpackNode.jsNode.jsNestJSNest.jsGoGolangPythonPythonFastAPIFastAPIPostgreSQLPostgreSQLMongoDBMongoDBPrismaPrismaGitGitLinuxLinuxFigmaFigmaClaudeClaudeCodexDeepSeekDeepSeek

In short

I'm not just interested in building an interface — I want to understand the whole problem: who needs the product, how it should work and what will help the team keep developing it. At Matrix IT I grew from a junior frontend developer into the person trusted with the shared architectural foundation, the documentation and the conventions. Today I own the technical direction of PinShop TJ and develop an approach to building software with Claude, Codex and Mimo — as tools that have to be managed properly.

The path

From school tasks in Sizhd to technical leadership in a marketplace

01 / 07

  1. SCHOOL YEARS · SIZHD

    Being useful first

    I come from the village of Sizhd in the Shughnan district of Tajikistan. My path into IT didn't start with a grand idea about a future profession — it started with ordinary school tasks.

    I helped teachers create and edit documents, prepared presentations for school competitions and sometimes helped run computer science classes. I enjoyed figuring out computers and using that knowledge where it was immediately useful.

    Over time it became clear: what fascinated me wasn't the computer itself, but the ability to solve concrete problems with it.

  2. THE SUMMER AFTER 10TH GRADE

    Teaching myself to code

    After surgery I temporarily couldn't do physical work. No drama in it: I simply had a summer I could invest in something new.

    I chose programming and started learning on my own from YouTube. I worked through lessons, repeated examples, made mistakes, returned to the parts I didn't understand and tried again. Within a few months I had more than a first practical foundation — my whole approach to learning changed: if I lack the knowledge a task needs, I can find the material, test it in practice and get to a working solution.

    I entered 11th grade not just interested in IT, but intending to build my own projects.

  3. 11TH GRADE · MAY 2024

    First product: learning built around actions

    My first significant project was an online learning platform in plain JavaScript. It had no backend, no user accounts and no role model. I focused on what I could genuinely build and show.

    Even then it mattered to me not to just assemble a set of pages. I thought about the person's scenario: what they would do on the platform and which tool they would need in a given section.

    1st placenational “Young Programmers” contest, May 2024

  4. SCHOOL PERIOD

    An olympiad and a demo that opened the next door

    In the same school period I reached the final, national stage of the computer science olympiad. I didn't win, but the result got me into another national IT competition. In the computer science category nobody reached the required minimum, so no prize was awarded. What I did get there was a meeting with the CEO of Matrix IT.

    A working demo often says more about your approach than a formal place in a competition.

  5. JUNE 2024 — APRIL 2026 · MATRIX IT

    From a first job to architectural influence

    After finishing school I was invited to Matrix IT without an interview. I started in June 2024, passed the probation period in a week and signed my first contract.

    The team had two frontend developers, two backend developers and a designer; a backend developer acted as team lead. I studied the codebase I inherited and noticed the frontend could be made more flexible and easier to reuse.

    In that time I learned that a strong technical decision isn't only code that works today. It's also a foundation that makes the next task clearer for the whole team.

  6. SEPTEMBER 2024 · TOMSK

    TUSUR: study alongside practice

    In September 2024 I moved to Tomsk and enrolled at TUSUR in software development at the faculty of computing systems. I combined studying with remote work at Matrix IT.

    University doesn't replace commercial practice for me — it systematises it. In work projects I meet real constraints, deadlines and architectural trade-offs. In study I strengthen the fundamentals and connect practical decisions to a broader engineering picture. Planned graduation: June 2028.

  7. APRIL 2026 — NOW · PINSHOP TJ

    The next level of responsibility

    After I left Matrix IT in April 2026, one of the company's founders reached out and offered me the technical lead role at PinShop TJ.

    PinShop TJ is being built for people in Tajikistan who find it hard to buy goods from China on their own. Not everyone has a foreign bank card, the language skills or a way to arrange affordable delivery. The product's job is to connect a localised shopping experience, payment and delivery into one clear process.

    The project is currently in testing. That's why I don't talk about a public launch or metrics that don't exist yet. My current task is to shape the product and the development process so every decision can be verified, weak spots can be found and the system can be prepared for the next stage step by step.

Cases

MATRIX IT · 2024

Vite and Feature-Sliced Design as a shared foundation

Build speed was the most visible problem. On my Celeron machine the Webpack project took over a minute to build. I put together a Vite prototype — the build took a few seconds. On more powerful machines the pain was weaker, but my computer showed clearly how expensive the old process was for development.

WEBPACK, BEFORE
> 60 s
VITE, AFTER
~ 3 s

After the demo the team moved to Vite and chose Feature-Sliced Design as its architectural foundation. I was trusted to build a template frontend codebase that could be adapted to different products through copy, environment variables and a visual theme.

MATRIX IT · 2024—2026

The Nadim ecosystem and CRM

I worked on the frontend of the Nadim ecosystem and CRM: point-of-sale interfaces, role-based access and secure app integrations.

My responsibility grew beyond individual screens. I made sure the architectural conventions were followed, helped the second frontend developer work inside the shared structure and wrote project documentation.

11TH GRADE · MAY 2024

A learning platform in plain JavaScript

On the platform you could watch lessons, read lectures and complete assignments. For different subjects I built separate tools: a console for computer science, a calculator for maths, a map for geography and other subject-specific elements.

IT COMPETITION · SCHOOL PERIOD

A multilingual interface assembled with a neural network

A small interface: three name fields in Russian, Tajik and English. Enter moved the focus forward and the active language was highlighted. At the time I was learning Angular and didn't know React yet.

Part of the solution I assembled with a neural network: I understood the result I wanted, could state the task and verify that the interface worked as intended. This was the demo the CEO of Matrix IT saw.

Working with AI

How I run development with AI

On PinShop TJ I use Claude, Codex and Mimo as a team of AI agents. They help explore the codebase, implement tasks, write tests, check hypotheses and find problems.

But AI doesn't decide what the product should be. I state the requirements, break the work down, make the architectural decisions, set the constraints and verify the result. Then I connect the separate changes into a coherent system and own its quality.

My Matrix IT experience turned out to be especially important here. Running agent-driven development takes more than writing a good prompt. It takes clear architecture, documentation, definitions of done and the ability to spot a solution that formally works but creates problems later.

Claude
codebase research, task decomposition
Codex
implementing changes and tests
Mimo
checking hypotheses, finding problems

Contact

Let's stay in touch

In the “AI in practice” channel I show development without the showcase: how I state requirements, make architectural decisions and use AI for real tasks. If you're looking for a technical partner for a digital product, I'd be glad to discuss it personally.

Channel

Decisions, mistakes and working habits, taken apart a few times a week.

Follow

Direct

The task, the timeline, the way we'd work — write and we'll figure it out.

Work together