Channel

Django darslari (Mukhammad irmatov)

@DjangoDarslari

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,251subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID	-1001231152360
Type	Channel
Username	@DjangoDarslari
Created	Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	13 August 2026
Measurements held	3
Confirmed unchanged	1 time, most recently 13 August 2026
On Telegram	t.me/DjangoDarslari

Growth

3 measurements spanning 6 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,251–1,253 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Aug 2026, 12:57	1,251	-2
7 Aug 2026, 22:49	1,253	no change
7 Aug 2026, 16:19	1,253	first reading

Engagement

18 posts held, back to 27 August 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 28 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime: 1m 52s
Average length: 56s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

500 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 38.4% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
👍	192	38.4%
🔥	151	30.2%
😁	48	9.60%
❤	29	5.80%
💯	27	5.40%
👨‍💻	12	2.40%
🤣	10	2.00%
⚡	8	1.60%
🎉	7	1.40%
👏	6	1.20%
👎	3	0.6%
😱	3	0.6%
🤩	3	0.6%
🫡	1	0.2%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 500reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 27 August 2024 to 28 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Jun 2026, 04:25 UTC728 views26 reactionsread 7 August 2026

Photo

Oldinlari startup qilish uchun ancha ter to‘kish kerak edi: haqiqiy muammoni topish, bozorni o‘rganish, tuzukroq jamoa yig‘ish va birinchi mijozlarni topish. Hozir esa vaziyat butunlay boshqacha: g‘oyani topamiz(buyam ChatGPT bilan), AI ga landing sayt tayyorlatamiz, 2 soatda Claude bilan demo tayyorlab qo’yamiz ammo na bitta foydalanuvchi, na pul to‘laydigan mijoz bor. AI dastur/ilova yasashni juda osonlashtirib yu…

💯26

Signed mukhammad irmatov

25 Jun 2026, 19:07 UTC808 views27 reactionsread 7 August 2026

Futbolcha mantiq IT’da bo‘lganda: loyiha ishlashi shart emas, muhimi eng zo‘r texnologiyalarda yozilgani, deyilardi.

😁14🤣10👍2👎1

Signed mukhammad irmatov

13 Oct 2025, 15:45 UTC≈3,200 views38 reactionsread 7 August 2026

Photo

Mana buni yangilik desa bo’ladi Vanihoyat python 3.14 versiyasida GIL ni olib tashladi. Endi CPU bound tasklarda parallelismni his qilib ko’rishinglar mumkin faqat race conditionlardan ehtiyot bo’lasiz )

👍15🔥12🎉4❤3👏2🤩2

Signed mukhammad irmatov

6 Aug 2025, 15:27 UTC≈3,760 views14 reactionsread 7 August 2026

Mohirdev marketing komandasiga yosh va kreativ jamoa yig’ilgan. Oxirgi vaqtlar ancha sifatli kontentlar qilishyapti, ko’z tegmasin.

👍7❤4⚡1👨‍💻1💯1

Signed mukhammad irmatov

6 Aug 2025, 15:27 UTC≈2,890 views28 reactionsread 7 August 2026

Forwarded from @mohirdevVideo

🖥 Pentium 3 vs elektrokar “Python Full Stack” kursimiz eksperti Muhammad Ermatovning hayoti shunaqa kontrastlardan iborat. Ba’zan ofisda, ba’zan tog‘ cho‘qqisida bo‘ladi. Lekin orada vaqt topib izohlaringizni o‘qishi mumkin 👇 #yuzmayuz @mohirdev

👍21🔥3❤2⚡1👏1

Signed mukhammad irmatov

30 May 2025, 19:08 UTC≈3,550 views22 reactionsread 7 August 2026

Oldin barcha loyihalarimda UUID ni ishlatar edim, yaqin 2-3 oydan beri ULID ni ishlatyapman. UUID dan ko’ra ancha qulay, o’qishga ham oson. ULID timestamp orqali yaratilgani uchun indekslar tartibli saqlanadi - insert/read ham UUID dan ko’ra tezroq. Oramizda ULID ni ishlatadiganlar bormi, nima uchun ULID ga o'tgansiz?

👨‍💻11👍8❤2👎1

Signed mukhammad irmatov

4 May 2025, 12:57 UTC≈4,570 views42 reactionsread 7 August 2026

Har qanday motivatsiyaga boy, auditoriyaga moslab aytilgan gaplarga ishonib, amal qilavermaslik kerak. “Dam olishsiz ishlash kerak, shunda top performer bo’ladi” deyish g’irt absurd tushuncha, ancha muncha zo’r dasturchilarni dam olishsiz(no weekend) ishlab burnout bo’lib qolganini ko’rganman, burnout bo’lgach 1-2 oy umuman kompyuterga yaqinlashmaganlari ham talaygina. Elon muskni o’zi “haftasiga 80-100 soat ishladim…

👍34❤3👏3🔥2

Signed mukhammad irmatov

4 May 2025, 12:57 UTC≈2,680 viewsread 7 August 2026

https://t.me/birfoizbilim/278

Signed mukhammad irmatov

3 Apr 2025, 16:10 UTC≈3,330 views34 reactionsread 7 August 2026

Photo

Oramizda Kwatt ilovasida ishlagan dasturchilar bo’lsa, iltimos Notification tizimiga qarab qo’yinglar, deyarli har doim 5-6 talab notification jo’natadi. Retry tizimi yaxshi ishlamayotgan bo’lishi, FCM tokenlarni saqlashda muammo bo’lishi ham mumkin. Yoki shunchaki, bildirishnoma yuborayotgan admin bir marta yuborish o’rniga knopkani 5-6 martalab bosyapti )

😁28👍5😱1

Signed mukhammad irmatov

27 Feb 2025, 17:46 UTC≈3,300 views30 reactionsread 7 August 2026

Overengineering — qanday oldini olish mumkin? Xo‘sh, overengineering to‘g‘ri ish emasligi haqida yozdik, lekin real loyihalarda undan qanday qochish mumkin? Muhimi – muammoga qarab emas, balki ehtiyojga qarab kod yozish kerak. Ko‘p hollarda, ortiqcha murakkablik dasturchining kelajakda yuzaga kelishi mumkin bo‘lgan muammolarni hozirdan "hal qilib qo’yish“ istagidan kelib chiqadi. Lekin bunday yondashuv amaliyotda 1…

👍18❤7🔥4🤩1

Signed mukhammad irmatov

27 Feb 2025, 13:05 UTC≈2,370 views30 reactionsread 7 August 2026

Overengineering — Katta muammolarga kichik yechim, kichik muammolarga katta yechim Dasturchilar loyiha boshlaganda yoki kod yozishda mukammallikni maqsad qilishadi. Har bir funksiya maksimal darajada reusable(qayta ishlatib bo’ladigan) bo‘lishi kerak, har bir mikroservis mustaqil ishlashi kerak, har bir metod kengaytiriladigan bo‘lishi kerak... Va oxir-oqibat, oddiy muammoni hal qilish uchun murakkab, boshqarish qiy…

🔥16👍11❤1👎1🫡1

Signed mukhammad irmatov

27 Feb 2025, 03:15 UTC≈2,260 views47 reactionsread 7 August 2026

Ko‘pchiligimiz Django va Python backend'da "best practices" izlaymiz, lekin aslida, yomon amaliyotlar (anti-patternlar) dan qochish hammasidan ko’ra muhimroq. Masalan, CI pipeline umuman bo‘lmasligi, yoki aksincha, 30+ daqiqada test o‘tishi, PR merge qilish uchun butun jamoaning approve berishini kutish — bular jamoaning tezligini pasaytiradi. Gitflow branch strategiyasi esa Django monolit yoki microservice ishlatila…

🔥37👍9😁1

Signed mukhammad irmatov

Showing the 12 most recent of 18 posts we hold for @DjangoDarslari. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Jakhongir Rakhmonov - IT
@jakhonrakhmonov · 9,3701 post MohirDev.uz
@mohirdev · 19,3451 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

1% Bilim
@birfoizbilim · 14,4031 post Jakhongir Rakhmonov - IT
@jakhonrakhmonov · 9,3701 post MohirDev.uz
@mohirdev · 19,3451 post Работа на Python в Узбекистане | O'zbekistondagi Python bo'yicha vakansiyalar
@uzpythonjobs · 2,3191 post

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Django darslari (Mukhammad irmatov)” (@DjangoDarslari), 1,251 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DjangoDarslari.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.