Telegram RegisterThe public register of Telegram
Telegram profile photo for Programmer City «شهر برنامه‌نویس»

Channel

Programmer City «شهر برنامه‌نویس»

@programercity

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

1,147subscribers

+1 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
TypeChannel
Username@programercity
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/programercity

Growth

1,1431,1541,148.57 August 2026 — 1,146 subscribers7 August 2026 — 1,146 subscribers7 August 2026 — 1,148 subscribers10 August 2026 — 1,149 subscribers13 August 2026 — 1,143 subscribers17 August 2026 — 1,154 subscribers20 August 2026 — 1,151 subscribers23 August 2026 — 1,147 subscribers1,1477 August 202623 August 2026
8 measurements spanning 16 days, net +1. 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,141–1,156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 12:261,147-4
20 Aug 2026, 05:371,151-3
17 Aug 2026, 12:051,154+11
13 Aug 2026, 17:541,143-6
10 Aug 2026, 21:311,149+1
7 Aug 2026, 15:071,148+2
7 Aug 2026, 01:161,146no change
7 Aug 2026, 01:031,146first reading

Engagement

20 posts held, back to 2 August 2026the 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.

ERR · 30 days
2.43%
avg views ÷ 1,147 subscribers
Avg views / post
27.9
19 posts measured
Reaction rate
5.18%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 17 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (2 August 20266 August 2026)
Views total530
Reactions total26
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

26 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 34.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
934.6%
🔥934.6%
🏆415.4%
👏27.69%
😍27.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 26reactions 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

6 Aug 2026, 20:38 UTC7 viewsread 7 August 2026

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

6 Aug 2026, 12:47 UTC17 views2 reactionsread 7 August 2026

🎯 تمرین امروز ProgrammerCity فرض کن این Task بهت داده شده: «به اپلیکیشن، قابلیت ثبت‌نام کاربر اضافه کن.» ❓ قبل از اینکه شروع به کدنویسی کنی، حداقل ۳ سؤال از کسی که Task رو بهت داده میپرسی؟ سؤالاتت رو همین‌جا بنویس. 👇 مثلاً: 🔹 چه اطلاعاتی باید از کاربر دریافت بشه؟ اما سعی کن سؤال‌های خودتو پیدا کنی. 😉 📅 قسمت بعدی: 🧪 چرا برنامه‌نویس‌های حرفه‌ای قبل از تحویل Task، خودشون کدشونو تست میکنن؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜

1🔥1

6 Aug 2026, 09:09 UTC20 views2 reactionsread 7 August 2026

📝 برای تحلیل یک Task، اول باید ابهام‌ها رو از بین ببری. مثلاً برای قابلیت جستجوی محصولات، میتونی بپرسی: 🔹 جستجو بر اساس نام محصوله یا دسته‌بندی هم شامل میشه؟ 🔹 اگر نتیجه‌ای پیدا نشد، چه چیزی نمایش داده بشه؟ 🔹 جستجو باید لحظه‌ای باشه یا بعد از زدن دکمه؟ 🔹 حروف بزرگ و کوچک اهمیت دارن؟ 🔹 نتیجه‌ها چطور مرتب بشن؟ بعد از مشخص شدن این موارد، Task خیلی واضح‌تر میشه. 📌 برنامه‌نویس حرفه‌ای سریع‌تر کد نمیزنه؛ قبل از کدنویسی

1🔥1

6 Aug 2026, 07:15 UTC17 views2 reactionsread 7 August 2026

💼 از دانشگاه تا شرکت 🚀 فصل دوم | قسمت ششم 📝 قبل از کدنویسی، Task رو تحلیل کن! 🎬 داستان امروز از یک روز واقعی در دنیای برنامه‌نویسی... یک Task بهت داده شده: «قابلیت جستجوی محصولات رو به سایت اضافه کن.» خب... میری سراغ کدنویسی؟ 💻 صبر کن! ✋ این جمله خیلی کلیه. قبل از اینکه حتی یک خط کد بنویسی، باید بفهمی: ❓ جستجو دقیقاً باید چطور کار کنه؟ و همین‌جا مهارت مهمی به اسم Task Analysis وارد ماجرا میشه. ━━━━━━━━━━━━

1🔥1

5 Aug 2026, 09:55 UTC30 views2 reactionsread 7 August 2026
Poll

اینجا مشخص کن😁

  1. 1️⃣11%
  2. 2️⃣0%
  3. 3️⃣78%
  4. 4️⃣11%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1🔥1

5 Aug 2026, 09:54 UTC26 views1 reactionsread 7 August 2026

🎯 یک موقعیت واقعی: لید تیم ازت میپرسه: «این قابلیت رو کی میتونی تحویل بدی؟» تو هنوز دقیقاً پروژه رو بررسی نکردی. چه جوابی میدی؟ 1️⃣ «امروز تمومش میکنم.» 2️⃣ «فکر کنم دو روز زمان ببره.» 3️⃣ «اجازه بده اول Task رو بررسی کنم، بعد زمان دقیق‌تری بهت بدم.» 4️⃣ «نمیدونم.» 👇 شماره گزینه رو مشخص کن. 📅 فردا میریم سراغ قدمی که قبل از تخمین زمان باید انجام بدی: 📝 چطور یک Task رو درست تحلیل کنیم؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜ 𝙋

😍1

5 Aug 2026, 09:53 UTC21 views2 reactionsread 7 August 2026

⏳ تخمین زمان یعنی قبل از شروع کار، حدس بزنیم انجام یک Task واقعاً چقدر زمان میبره. اما یک اشتباه رایج وجود داره: ❌ «فکر کنم دو ساعت طول بکشه.» برنامه‌نویس حرفه‌ای قبل از تخمین، اول Task رو بررسی میکنه. مثلاً: 🔹 دقیقاً چه چیزی باید ساخته بشه؟ 🔹 چه بخش‌هایی باید تغییر کنن؟ 🔹 آیا با بخش ناشناخته‌ای از پروژه روبه‌رو هستیم؟ 🔹 نیاز به تست داریم؟ 🔹 احتمال وجود مشکل یا وابستگی وجود داره؟ 📌 تخمین خوب یعنی حدس زدنِ شانسی

🏆2

5 Aug 2026, 09:17 UTC26 views2 reactionsread 7 August 2026

🚀 فصل دوم | قسمت پنجم ⏳ چرا برنامه‌نویس‌ها گاهی زمان انجام یک تسکو اشتباه تخمین میزنن؟ 🎬 داستان امروز از یک روز واقعی در دنیای برنامه‌نویسی... لید تیم میاد سراغت: «این قابلیتو تا فردا میتونی تحویل بدی؟» تو هم با اعتمادبه‌نفس میگی: «آره، فکر کنم چند ساعت بیشتر طول نکشه.» ⏰ فردا میشه... هنوز کارت تموم نشده! یک باگ پیدا کردی، یک بخش پروژه رو بهتر نفهمیدی و یک مشکل دیگه هم وسط کار به وجود اومده. حالا سؤال: ❓ مش

2

4 Aug 2026, 20:25 UTC31 views1 reactionsread 7 August 2026
Poll

اینجا بگو👀

  1. 1️⃣29%
  2. 2️⃣14%
  3. 3️⃣0%
  4. 4️⃣57%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

1

4 Aug 2026, 20:24 UTC33 views1 reactionsread 7 August 2026

💬 اگر قرار باشه در یک Daily Stand-up شرکت کنی، به نظرت گفتن کدوم مورد از همه مهم‌تره؟ 1️⃣ کارهایی که دیروز انجام دادی. 2️⃣ برنامه امروزت. 3️⃣ مشکلی که باعث شده نتونی ادامه بدی. 4️⃣ هر سه مورد به یک اندازه مهم هستن. شماره گزینه رو مشخص کن. 👇 📅 در قسمت بعدی وارد یکی از مهم‌ترین مهارت‌های جونیورها میشیم: چطور زمان انجام یک تسکو درست تخمین بزنیم و چرا نباید قول‌های غیرواقعی بدیم؟ ━━━━━━━━━━━━━━━━━━ °⋆⸜ 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝙢𝙚𝙧'𝙨

🔥1

4 Aug 2026, 20:24 UTC28 views1 reactionsread 7 August 2026

💡 هدف 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.

5 Aug 2026, 09:55 UTCAnonymous Poll9 voters

اینجا مشخص کن😁

  1. 1️⃣11%
  2. 2️⃣0%
  3. 3️⃣78%
  4. 4️⃣11%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

4 Aug 2026, 20:25 UTCAnonymous Poll7 voters

اینجا بگو👀

  1. 1️⃣29%
  2. 2️⃣14%
  3. 3️⃣0%
  4. 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.

Citation-graph rank

Citation-graph rank — 745,593 of 1,602,868entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 31 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.

EngineeringReverse | مهندسی معکوس
@EngineeringReverse · 19,830
3 posts
English Unique | آموزش زبان انگلیسی
@english_uniquee · 19,101
3 posts
مهدی هک | آموزش هک و امنیت™
@Mahdiihack · 20,160
3 posts
سفارش پروژه | پروژه بگیر 🥇
@prozhebegir_ir · 16,949
3 posts
آزمون طراحی معماری نظام مهندسی
@tarrahimemari · 11,440
3 posts
❰❰ آموزش مقاله‌نویسی ISI ❱❱
@akhtar_electronic_group · 19,251
2 posts
Arras and Design
@Design_groooup · 12,410
2 posts
English online
@Eng_Online · 36,640
2 posts
آنلاین استخدام
@estekhdam_online2 · 251
2 posts
ʜɪʀᴀ ᴘʀᴏᴊᴇᴄᴛ
@Hiraproje · 297
2 posts
ModirShabake
@modirshabake · 11,810
2 posts
💻 programmer_best
@programmer_best · 14,412
2 posts
سریال روم | فیلم و سریال
@SeriallRoom · 11,255
2 posts
کامپیوتر و نرم‌افزار
@spcware · 12,936
2 posts
VOXEL 3D OBJECT
@Voxel3DDVray · 12,313
2 posts
Voxel Object Revit
@VoxelObjectRevit · 11,562
2 posts
🌸آرامش با داستان🌸
@arameshbadastan · 10,095
1 post
English Literature
@Englishliteraturemagazine · 11,461
1 post
🚨استخدامی فوری تهران و ایران
@estekhdami_fouri · 7,917
1 post
پــروژه|𝙆𝙖𝙧𝙞𝙣𝙤
@Nab_project · 6,561
1 post
هوش مصنوعی
@prompt405 · 664
1 post
مرکز تعمیرات موبایل
@repairms · 23,185
1 post
کانال آموزش مقاله نویسی + چاپ کتاب + آموزش از 0 تا 100 با شما هستیم
@resumedaran · 15,211
1 post
تبلیغات دانشجویی
@tablighaht · 1,352
1 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“Programmer City «شهر برنامه‌نویس»” (@programercity), 1,147 subscribers as measured 23 August 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.