Python backends and AI, built for production.
I'm Fazliddin. I design the data model, write the service layer, ship it, and keep it alive — lately with LLM agents, document extraction and computer vision for real businesses.
- ~4 yearsPython backend & DevOps
- AI in productionlogistics · agriculture · manufacturing
- Namangan, UZGMT+5 · 4 languages
The stack I ship with
Applied AI in boring, important places.
Not demos — systems where a wrong answer costs someone money. Client names are always anonymized.
-
AI back office for a trucking company
~150 trucks on CIS, Turkey and China routes. A Telegram agent reads contracts, licences and passports with an LLM — and never quietly saves a wrong number.
Read the write-up -
Guardrails for an LLM agent
The prompt asks, the code enforces: a small Python layer that keeps tool names, tracebacks and four-paragraph answers away from users.
Read the write-up -
Visual product search
Snap a photo, get the matching catalogue item back in Telegram. DINOv2 embeddings and one matrix multiply — on a MacBook, no vector database.
Read the write-up -
On-prem vision for a factory
Face ID attendance, scale events and future camera AI for a ~200-person plant — one server, sized GPU-ready rather than GPU-first.
How I can help.
Fixed-scope projects or hourly work. Tell me what you need and when — I reply within one business day.
Web application
Full-stack web app with Django or Next.js. Database, auth, admin panel, deployment included.
Telegram bot
Custom Telegram bot for your business — orders, notifications, CRM integration, payments.
Automation & API
Automate repetitive tasks, build REST APIs, connect third-party services, set up CI/CD.
Hourly work
Bug fixes, small features, code review, server setup — anything you need, billed by the hour.
Write-ups from production.
What broke, what I changed, and the code that fixed it.
All postsVisual Product Search on a Laptop with DINOv2 (No Vector DB Required)
Snap a photo, get the matching catalogue item. ~700 images, one MacBook, one matrix multiply.
The Prompt Asks, the Code Enforces: Guardrails for an LLM Agent in Production
Verbose replies, leaked tool names, and raw exceptions in front of users — and the small Python layer that fixed them.
Never Let the Model Save: LLM Document Extraction in a Trucking Back Office
Two rules that made AI document extraction safe enough for a business where a wrong number becomes a wrong tax payment.
Lessons I keep relearning.
“The prompt asks. The code enforces. Don't ship an agent with only one of them.”
“LLMs are great readers and terrible accountants. Let them read. Show a human what they read.”
“A pretrained model, a normalized matrix, and a threshold will get you surprisingly far.”
Have a system that has to be right? Let's build it.
Tell me what you're building and where it hurts. Rules that cost money go in one tested place — never in a prompt.