💯 دو ساعت دیگه پاک میشه . . . 🗓 🧨 https://t.me/addlist/oUIpXumgFB1lMzlk .

Channel
Programmer City «شهر برنامهنویس»
@programercity
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,072subscribers
-74 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 | -1001593369313 |
|---|---|
| Type | Channel |
| Username | @programercity |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/programercity |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 18:19 | 1,072 | -9 |
| 11 Nov 2026, 10:07 | 1,081 | -3 |
| 7 Nov 2026, 08:55 | 1,084 | -6 |
| 4 Nov 2026, 10:39 | 1,090 | -1 |
| 30 Oct 2026, 03:48 | 1,091 | -3 |
| 27 Oct 2026, 03:21 | 1,094 | -1 |
| 24 Oct 2026, 08:26 | 1,095 | -8 |
| 21 Oct 2026, 11:46 | 1,103 | -5 |
| 15 Oct 2026, 09:06 | 1,108 | -4 |
| 12 Oct 2026, 00:15 | 1,112 | -9 |
| 5 Oct 2026, 02:17 | 1,121 | -14 |
| 26 Sept 2026, 08:20 | 1,135 | -12 |
| 17 Sept 2026, 08:01 | 1,147 | -6 |
| 13 Sept 2026, 08:16 | 1,153 | +3 |
| 9 Sept 2026, 17:39 | 1,150 | -8 |
| 4 Sept 2026, 16:02 | 1,158 | +16 |
| 1 Sept 2026, 06:48 | 1,142 | -7 |
| 29 Aug 2026, 09:37 | 1,149 | +7 |
| 26 Aug 2026, 03:24 | 1,142 | -5 |
| 23 Aug 2026, 12:26 | 1,147 | first reading |
Engagement
20 posts held, back to 2 August 2026 — 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 page of 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
26 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 34.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 34.6% | |
| 🔥 | 9 | 34.6% | |
| 🏆 | 4 | 15.4% | |
| 👏 | 2 | 7.69% | |
| 😍 | 2 | 7.69% |
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 20 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 August 2026 to 6 August 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
🎯 تمرین امروز ProgrammerCity فرض کن این Task بهت داده شده: «به اپلیکیشن، قابلیت ثبتنام کاربر اضافه کن.» ❓ قبل از اینکه شروع به کدنویسی کنی، حداقل ۳ سؤال از کسی که Task رو بهت داده میپرسی؟ سؤالاتت رو همینجا بنویس. 👇 مثلاً: 🔹 چه اطلاعاتی باید از کاربر دریافت بشه؟ اما سعی کن سؤالهای خودتو پیدا کنی. 😉 📅 قسمت بعدی: 🧪 چرا برنامهنویسهای حرفهای قبل از تحویل Task، خودشون کدشونو تست میکنن؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜…
❤1🔥1
📝 برای تحلیل یک Task، اول باید ابهامها رو از بین ببری. مثلاً برای قابلیت جستجوی محصولات، میتونی بپرسی: 🔹 جستجو بر اساس نام محصوله یا دستهبندی هم شامل میشه؟ 🔹 اگر نتیجهای پیدا نشد، چه چیزی نمایش داده بشه؟ 🔹 جستجو باید لحظهای باشه یا بعد از زدن دکمه؟ 🔹 حروف بزرگ و کوچک اهمیت دارن؟ 🔹 نتیجهها چطور مرتب بشن؟ بعد از مشخص شدن این موارد، Task خیلی واضحتر میشه. 📌 برنامهنویس حرفهای سریعتر کد نمیزنه؛ قبل از کدنویسی…
❤1🔥1
💼 از دانشگاه تا شرکت 🚀 فصل دوم | قسمت ششم 📝 قبل از کدنویسی، Task رو تحلیل کن! 🎬 داستان امروز از یک روز واقعی در دنیای برنامهنویسی... یک Task بهت داده شده: «قابلیت جستجوی محصولات رو به سایت اضافه کن.» خب... میری سراغ کدنویسی؟ 💻 صبر کن! ✋ این جمله خیلی کلیه. قبل از اینکه حتی یک خط کد بنویسی، باید بفهمی: ❓ جستجو دقیقاً باید چطور کار کنه؟ و همینجا مهارت مهمی به اسم Task Analysis وارد ماجرا میشه. ━━━━━━━━━━━━…
❤1🔥1
اینجا مشخص کن😁
- 1️⃣11%
- 2️⃣0%
- 3️⃣78%
- 4️⃣11%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤1🔥1
🎯 یک موقعیت واقعی: لید تیم ازت میپرسه: «این قابلیت رو کی میتونی تحویل بدی؟» تو هنوز دقیقاً پروژه رو بررسی نکردی. چه جوابی میدی؟ 1️⃣ «امروز تمومش میکنم.» 2️⃣ «فکر کنم دو روز زمان ببره.» 3️⃣ «اجازه بده اول Task رو بررسی کنم، بعد زمان دقیقتری بهت بدم.» 4️⃣ «نمیدونم.» 👇 شماره گزینه رو مشخص کن. 📅 فردا میریم سراغ قدمی که قبل از تخمین زمان باید انجام بدی: 📝 چطور یک Task رو درست تحلیل کنیم؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜ 𝙋…
😍1
⏳ تخمین زمان یعنی قبل از شروع کار، حدس بزنیم انجام یک Task واقعاً چقدر زمان میبره. اما یک اشتباه رایج وجود داره: ❌ «فکر کنم دو ساعت طول بکشه.» برنامهنویس حرفهای قبل از تخمین، اول Task رو بررسی میکنه. مثلاً: 🔹 دقیقاً چه چیزی باید ساخته بشه؟ 🔹 چه بخشهایی باید تغییر کنن؟ 🔹 آیا با بخش ناشناختهای از پروژه روبهرو هستیم؟ 🔹 نیاز به تست داریم؟ 🔹 احتمال وجود مشکل یا وابستگی وجود داره؟ 📌 تخمین خوب یعنی حدس زدنِ شانسی…
🏆2
🚀 فصل دوم | قسمت پنجم ⏳ چرا برنامهنویسها گاهی زمان انجام یک تسکو اشتباه تخمین میزنن؟ 🎬 داستان امروز از یک روز واقعی در دنیای برنامهنویسی... لید تیم میاد سراغت: «این قابلیتو تا فردا میتونی تحویل بدی؟» تو هم با اعتمادبهنفس میگی: «آره، فکر کنم چند ساعت بیشتر طول نکشه.» ⏰ فردا میشه... هنوز کارت تموم نشده! یک باگ پیدا کردی، یک بخش پروژه رو بهتر نفهمیدی و یک مشکل دیگه هم وسط کار به وجود اومده. حالا سؤال: ❓ مش…
❤2
Sticker, posted without a caption
اینجا بگو👀
- 1️⃣29%
- 2️⃣14%
- 3️⃣0%
- 4️⃣57%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤1
💬 اگر قرار باشه در یک Daily Stand-up شرکت کنی، به نظرت گفتن کدوم مورد از همه مهمتره؟ 1️⃣ کارهایی که دیروز انجام دادی. 2️⃣ برنامه امروزت. 3️⃣ مشکلی که باعث شده نتونی ادامه بدی. 4️⃣ هر سه مورد به یک اندازه مهم هستن. شماره گزینه رو مشخص کن. 👇 📅 در قسمت بعدی وارد یکی از مهمترین مهارتهای جونیورها میشیم: چطور زمان انجام یک تسکو درست تخمین بزنیم و چرا نباید قولهای غیرواقعی بدیم؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜ 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝙢𝙚𝙧'𝙨 …
🔥1
💡 هدف Daily Stand-up گزارش دادن به مدیر نیست. هدف اینه که اعضای تیم از وضعیت هم باخبر باشن و اگر کسی به کمک نیاز داره، سریع مشخص بشه. معمولاً هر نفر به سه سؤال جواب میده: ✅ دیروز روی چه کاری کار کردم؟ ✅ امروز روی چه کاری کار میکنم؟ ✅ آیا مانعی برای ادامه کار دارم؟ 📌 اگر جلسه بیشتر از چند دقیقه طول بکشه، احتمالاً از هدف اصلی خودش دور شده. ━━━━━━━━━━━━━━━━━━ °⋆⸜ 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝙢𝙚𝙧'𝙨 𝘾𝙞𝙩𝙮 ⸝⋆° ➤ Code • Learn • Build ➤ @…
👏1
Showing the 12 most recent of 20 posts we hold for @programercity. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
اینجا مشخص کن😁
- 1️⃣11%
- 2️⃣0%
- 3️⃣78%
- 4️⃣11%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
اینجا بگو👀
- 1️⃣29%
- 2️⃣14%
- 3️⃣0%
- 4️⃣57%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 2 August 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Named by 35 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@Eng_Online · 36,3395 postsEngineeringReverse | مهندسی معکوس
@EngineeringReverse · 21,8415 postsمهدی هک | آموزش هک و امنیت™
@Mahdiihack · 20,4515 postsسفارش پروژه | پروژه بگیر 🥇
@prozhebegir_ir · 17,3815 postsArras and Design
@Design_groooup · 12,5884 posts💻 programmer_best
@programmer_best · 14,8654 postsکامپیوتر و نرمافزار
@spcware · 13,7204 postsآزمون طراحی معماری نظام مهندسی
@tarrahimemari · 11,6774 postsVOXEL 3D OBJECT
@Voxel3DDVray · 12,8344 posts❰❰ آموزش مقالهنویسی ISI ❱❱
@akhtar_electronic_group · 19,8983 postsChilliTech | چیلی تک
@ChilliTech · 9,9243 postsEnglish Unique | آموزش زبان انگلیسی
@english_uniquee · 19,4283 postsمرکز تعمیرات موبایل
@repairms · 23,7103 postsVoxel Object Revit
@VoxelObjectRevit · 12,1173 postsبیمکس دیزایــن | 𝐁𝐦𝐚𝐱𝐝𝐞𝐬𝐢𝐠𝐧
@bmaxdesign · 28,5972 postsتور چالش و تست های انگلیسی
@en_quizztour · 7,2622 postsآنلاین استخدام
@estekhdam_online2 · 3382 posts🚨استخدامی فوری تهران و ایران
@estekhdami_fouri · 6,6652 postsʜɪʀᴀ ᴘʀᴏᴊᴇᴄᴛ
@Hiraproje · 3602 postsModirShabake
@modirshabake · 14,6312 postsپــروژه|𝙆𝙖𝙧𝙞𝙣𝙤
@Nab_project · 6,3821 post🔹️Proje miluni🔹️
@PROAJECTE · 17,2001 postتبلیغات دانشجویی
@tablighaht · 5,0431 postUnii_kar
@unii_kar · 23,6351 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Programmer City «شهر برنامهنویس»” (@programercity), 1,072 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/programercity.
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.