Channel
@aminrbg
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
653subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001988710808 |
|---|---|
| Type | Channel |
| Username | @aminrbg |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/aminrbg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 00:24 | 653 | -1 |
| 21 Aug 2026, 13:57 | 654 | -4 |
| 15 Aug 2026, 02:57 | 658 | -1 |
| 8 Aug 2026, 02:35 | 659 | no change |
| 7 Aug 2026, 20:11 | 659 | first reading |
20 posts held, back to 8 September 2025 — 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 20 posts for this entry, the most recent from 3 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
197 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 39.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 77 | 39.1% | |
| 👍 | 60 | 30.5% | |
| 🔥 | 55 | 27.9% | |
| 👎 | 3 | 1.52% | |
| 👏 | 2 | 1.02% |
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 19 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 197reactions 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 8 September 2025 to 3 January 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @aminrbg. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 8 September 2025 to 3 January 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
از ریپوهای جالبی که اخیراً به چشمم خورد، ریپوی about-me از آقای Bruce Wang، دایرکتور مهندسی نتفلیکسه. ایشون توی یه بخشی خلاصهٔ فیدبکهایی که توی ارزیابی ۳۶۰درجه بهش دادن رو هرسال به شکل عمومی منتشر میکنه: feedback @aminrbg
❤8
سال ۲۰۲۵ برای من پر بود از تغییر و جابجایی. توی این پست میتونین خلاصهای ازش رو بخونین. 2025 in Review @aminrbg
❤15👍1
پنجشنبهٔ هفتهٔ پیش دربارهٔ تغییرات اخیر در هوش مصنوعی، تأثیراتش روی آیندهٔ کار، و کارهایی که ما میتونیم برای بهره گرفتن از شرایط موجود انجام بدیم صحبت کردیم. اینجا میتونید محتوای متنی ارائه رو ببینید: AI Changes and Their Impact on Software Engineering این چندتا نوشته و پادکست هم در ارائه بهش اشاره شد که اینجا میذارم: - The 70% problem: Hard truths about AI-assisted coding - How Block is becoming the most AI-n…
❤13
ده دقیقهٔ دیگه شروع میکنیم 🙂 https://meet.google.com/erc-paet-bec
جهت یادآوری، اگر هنوز به کلندرتون اضافه نکردین، این ارائه فرداشب برگزار میشه. در ضمن خوشحال میشم پست بالا رو به دست کسایی که عضو کانال نیستن و به موضوع کنجکاون برسونین. میبینمتون.
❤2👍2
🎙 تکتاک: تغییرات هوش مصنوعی و آیندهٔ بازار کار مهندسی نرمافزار پنجشنبهٔ این هفته قراره که به مدت یک ساعت دربارهٔ تغییرات اخیر هوش مصنوعی و تأثیری که روی شرکتهای تکنولوژی گذاشته صحبت کنیم. همچنین نگاهی میکنیم به اینکه الان در چه وضعیتی قرار داریم و مهمتر از همه، چه کارهایی میتونیم انجام بدیم تا شغل و مسیر حرفهایمون رو امنتر نگه داریم و از فرصتهای موجود بیشترین استفاده رو ببریم. 📅 پنجشنبه ۲۹ آبان (20 Nov…
🔥19❤1
توی این سه تا پست از چند شیوه برای آماده شدن در برابر مشکلات پیشبینینشدهی زیرساخت یا لودهای ناگهانی نوشتم: ⛳ ارائه سرویس در سطوح مختلف با کمک Feature Flagها ⬇️ تعریف سطوح کاهش سرویس (Degradation Levels) 🔗 جلوگیری از اثر زنجیرهای در سرویسها (Cascading Effect) این اقدامات فقط مختص به شرایط بحرانیِ غیرمنتظره نیستن و در زمانهای فشار پیشبینیپذیر هم کاملاً کاربرد دارن. مثلاً همین چند هفتهٔ دیگه بلکفرایدی رو پیش …
❤8👏2
جلوگیری از اثر زنجیرهای در سرویسها (Cascading Effect) هر محصول از چندین برنامهٔ قابلاجرا تشکیل شده که با رشد تیم و وسعت محصول، تعدادشون کمکم به دهها یا حتی صدها برنامه میرسه. سازمانها معمولاً سرویسها رو بر اساس اهمیت به چند سطح تقسیم میکنن: tier1، tier2، ... تا برای هر سطح SLA، آنکال، و ظرفیت منابع متفاوتی تعریف کنن. به عنوان نمونه در مثال دیجیکالا، اپلیکیشن ثبت سفارش میتونه tier1 باشه چون مستقیم روی درآم…
👍8❤1
تعریف سطوح کاهش سرویس (Degradation Levels) با داشتن feature flagها میتونیم سطوح از پیش تعریف شدهای برای کاهش کنترلشدهی سرویس تعریف کنیم. یعنی اگر سیستم تحت فشار شدید قرار گرفت، به جای مواجه شدن با قطعی کامل، بهصورت مرحلهبهمرحله بعضی فیچرها رو از دسترس خارج کنیم. این کار کمک میکنه که عملکرد بخشهای اصلی پایدارتر بمونه چون هم محاسبات کمتری صورت میگیره، و هم منابعی آزاد میشه که برای scale up کردن بخشهای مه…
👍5❤1
امکان سرویسدهی در سطوح مختلف به کمک Feature Flagها هر محصول در کنار خدمترسانی اصلیش، کلی قابلیت و فیچر جانبی داره که باعث میشن تجربهٔ کاربر بهتر بشه و یا درآمدش بالاتر بره. مثلاً توی یه فروشگاه مثل دیجیکالا، علاوه بر مسیر اصلی تجربهٔ کاربر، یعنی جستجو، مشاهدهٔ محصول، اضافه کردن به سبد خرید، پرداخت و ثبت سفارش، دهها قابلیت دیگه هم وجود داره: لایو اینفلونسرها، سیستم recommendation، تبلیغات فروشندهها، ثبتنام و اح…
👍7❤3
چه زمانی برای شما مناسبه؟ (قابلیت انتخاب چند گزینه)
The shares total 130%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🔥4
قبل از شروع این سری پستها، یه پرانتز باز کنم. میخوام طی هفتههای آینده یه جلسه گفتوگوی آنلاین یک ساعته با شما داشته باشم دربارهی تغییرات اخیر بازار کار و layoffهای جدید تحت تأثیر AI، اینکه الان در چه وضعیتی هستیم و در شرایط جدید چه اقداماتی خوبه که انجام بدیم صحبت کنیم. اگر به شرکت در چنین گفتوگویی علاقهمندین، چه روز و ساعتی براتون مناسبتره؟ (به وقت ایران) 👇
❤9
Showing the 12 most recent of 20 posts we hold for @aminrbg. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
چه زمانی برای شما مناسبه؟ (قابلیت انتخاب چند گزینه)
The shares total 130%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 8 September 2025 to 3 January 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“امین رشیدبیگی | مهندسی نرمافزار” (@aminrbg), 653 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/aminrbg.
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.