3 measurements spanning 9 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 151–152 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 19:57
152
+1
8 Aug 2026, 19:45
151
no change
7 Aug 2026, 23:35
151
first reading
Engagement
20 posts held, back to 27 February 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.
ERR · 30 days
82.9%
avg views ÷ 152 subscribers
Avg views / post
126
2 posts measured
Reaction rate
9.52%
reactions ÷ views · ER floor
Posts in window
2
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 27 July 2026
Posts held
20 (27 February 2025 – 27 July 2026)
Views total
252
Reactions total
24
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 19:45 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
137 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 27.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
37
27.0%
👍
28
20.4%
🔥
28
20.4%
👨💻
15
10.9%
👏
12
8.76%
⚡
8
5.84%
👾
3
2.19%
❤🔥
2
1.46%
🙏
2
1.46%
🏆
1
0.73%
💩
1
0.73%
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 18 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 137reactions 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 27 February 2025 to 27 July 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.
Новая реальность: AI-риск живёт по обе стороны промпта
За одну неделю — две новости, которые отлично дополняют друг друга.
В первой топ-менеджер московской компании загружала конфиденциальные рабочие документы в DeepSeek. Её уволили за разглашение коммерческой тайны, а суд отказался восстанавливать на работе и выплачивать пять миллионов рублей компенсации.
Во второй автономный AI-агент во время тестирования вышел …
Что такое harness и почему все вдруг про это говорят?
Я задумывал этот канал, чтобы писать про всякие инженерные штуки простым человеческим языком. А потом нам завезли LLM. И мне как-то стало не до этого: появились новые инструменты и эксперименты с ними. Да и, если честно, мне показалось, что писать посты больше нет смысла — любой может написать промпт и всё для себя выяснить. В общем, меня немного завалило другими …
Начал таять снег и этот канал тоже начал оттаивать :)
Я хочу поделиться как можно использовать notebook lm - предыдущий пост создан при помощи него, вот ссылка на блокнот
Ловушка продуктивности: что на самом деле нужно измерять в эпоху ИИ?
Многие компании сейчас пытаются измерить эффективность разработчиков через количество промптов или процент кода, написанного нейросетью. Это путь в никуда.
Вот иерархия метрик, которые действительно имеют значение для бизнеса, а не просто создают видимость работы:
1. Метрики результата (Outcome Metrics) — Высшая ценность
Это «золотой стандарт» (м…
Москва, ГААААЗ вместе писать код
Уже 28 февраля в офисе МТС Банка пройдёт Код-ретрит — бесплатное мероприятие для практиков разработки. Без давления сроков сфокусируетесь на улучшении инженерных методов, таких как парное программирование и TDD.
Считаем, что лучше возможности обменяться опытом кодинга и выйти на новый уровень уже не будет 😎
🫵🏻 Ждём ваши заявки на участие на сайте. Как всегда, количество мест огран…
Привет! Уже на следующей неделе "Стачка" в Ульяновске, у меня есть один билет на конференцию, нашите комментарий к этому посту если хотите его получить. Cегодня разыграю билет среди откликнувшихся 🎫
🔥6👍2👨💻2
Showing the 12 most recent of 20 posts we hold for @smth_on_prog_lang. 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.
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.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“Что-то на разработческом” (@smth_on_prog_lang), 152 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/smth_on_prog_lang.
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.