Канал Александра Поломодова (@apolomodov), cto & technical fellow.
polomodov.tech - сайт со всеми материалами
youtube.com/@tellmeabouttech - канал со всеми видео
Created
Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
21 measurements spanning 24 days, net +893. 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 14,538–15,699 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)
Subscribers
Change
30 Aug 2026, 09:13
15,565
+50
29 Aug 2026, 08:05
15,515
+47
28 Aug 2026, 09:27
15,468
+138
27 Aug 2026, 06:47
15,330
+212
26 Aug 2026, 04:16
15,118
+273
25 Aug 2026, 01:59
14,845
+110
23 Aug 2026, 15:54
14,735
+5
22 Aug 2026, 01:39
14,730
+5
20 Aug 2026, 21:15
14,725
+8
19 Aug 2026, 19:37
14,717
+13
18 Aug 2026, 19:24
14,704
+8
17 Aug 2026, 16:05
14,696
+11
13 Aug 2026, 11:19
14,685
-1
12 Aug 2026, 09:02
14,686
-7
11 Aug 2026, 11:16
14,693
-5
10 Aug 2026, 11:20
14,698
+5
9 Aug 2026, 12:32
14,693
+4
8 Aug 2026, 09:12
14,689
-3
7 Aug 2026, 11:50
14,692
+15
6 Aug 2026, 10:30
14,677
first reading
Engagement
104 posts held, back to 31 July 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 46 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
14.5%
avg views ÷ 15,565 subscribers
Avg views / post
2,260
100 posts measured
Reaction rate
0.732%
reactions ÷ views · ER floor
Posts in window
101
of 104 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 30 August 2026
Posts held
104 (31 July 2026 – 30 August 2026)
Views total
225,656
Reactions total
1,636
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Aug 2026, 16:27 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.
What this channel posts
Photos
≈2,980
Videos
≈6
Links
≈2,390
Lifetime counters from Telegram’s own channel header, read 30 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
1,536 reactions across 97 posts, in 32 distinct kinds. The most used accounts for 32.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
497
32.4%
🔥
485
31.6%
👍
385
25.1%
😱
39
2.54%
🤔
16
1.04%
👎
13
0.846%
😢
13
0.846%
😁
12
0.781%
🫡
12
0.781%
💔
8
0.521%
🕊
7
0.456%
🌚
6
0.391%
👾
5
0.326%
💅
5
0.326%
🤝
5
0.326%
🗿
4
0.26%
😭
4
0.26%
✍
2
0.13%
❤🔥
2
0.13%
👌
2
0.13%
12 further kinds
14
0.911%
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 103 of the 104 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 1,665reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 104 most recent posts we hold, published 31 July 2026 to 30 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.
Telegram Stars
Stars received
9
across the posts below
Posts paid on
8
of 104 we hold a reading for · 8%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @book_cube. 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 104 most recent posts we hold for this entry, published 31 July 2026 to 30 August 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.
Code of Leadership S2E15 - Последние 90 дней в компании начинаются до заявления (Рубрика #Management)
Часть много говорят о первых 90 днях в новой роли. Мне захотелось разобрать обратную сторону перехода — последние 90 дней в компании. 31 августа в 17:00 проведу сольный эфир Code of Leadership где рассмотрю не только увольнение, но и все три равноправных исхода: остаться в пересобранной роли, перейти внутри компании…
Материалы 3 AImigo S1E3: почему AI дешевеет, а внедрение усложняется? (Рубрика #AI)
Готовы материалы третьего выпуска 3 AImigo, который вышел 28 августа. Вместе с Евгением Сергеевым и Алексеем Литвиновым мы впервые сделали совместный новостной дайджест: не прошлись по ленте анонсов, а собрали шесть связанных сюжетов вокруг одного сдвига. Модели и их использование дешевеют, а собрать из них работающую AI-систему стан…
Loop Engineering: агентный цикл как термостат, а не бесконечный bash (Рубрика #AI4SDLC)
В июле мы уже разбирали Loop Engineering с Максом Смирновым, но у слова loop есть ловушка: оно заставляет смотреть на повторение, хотя инженерная ценность начинается с обратной связи. В 18-минутном докладе «Loop Engineering from First Principles» Kyle Mistele предлагает воспринимать coding agent не как prompt, засунутый в бесконе…
Материалы выпуска с Антоном Костериным: как замкнуть AI-native SDLC? (Рубрика #AI4SDLC)
Готовы материалы 29-го выпуска Research Insights Made Simple, который прошёл 27 августа. Вместе с Антоном Костериным — principal engineer RnD-центра Т-Банка — разбирали "The AI-Native SDLC Playbook" от Anthropic: что должно измениться вокруг кодинга, чтобы скорость агентов превратилась в скорость поставки.
Обсудили:
- Почему pla…
Сергей Левин: почему акробатические трюки — плохой тест для робота (Рубрика #Robotics)
В мае я начал рубрику про робототехнику с вопроса: где реальный инженерный прогресс, а где хорошо поставленное демо? Интервью Сергея Левина, опубликованное 24 августа 2026 года, даёт полезный критерий: эффектный бэкфлип иногда говорит о будущем роботов меньше, чем скучная работа с незнакомой чашкой в новой комнате.
Левин — associ…
Dominika Rogala про выгорание: AI ускоряет работу — и поднимает норму нагрузки (Рубрика #Management)
В посте про AI-burnout речь шла о конечности человеческого внимания. Dominika Rogala добавляет организационный слой: AI может удешевить задачу и одновременно перегрузить рабочую систему. Инструменты стали быстрее — и ожидания тоже. Rogala — founder и leadership coach в Good Job Coffee, бывший VP of Engineering NeuroD…
Ищу человека, который подхватит AI4SDLC после меня (Рубрика #AI4SDLC)
31 августа я покидаю Т-Банк. Но задача, которой я занимался, остаётся: менять процессы разработки и вести компанию к AI Native.
Планка здесь высокая. Нужно знать передовые подходы, иметь hands-on опыт, уметь работать со множеством стейкхолдеров — и действительно хотеть изменить к лучшему одну из крупнейших технологических компаний России.
Про тек…
Research Insights Made Simple #29 про «The AI-Native SDLC playbook» с Антоном Костериным (Рубрика #AI4SDLC)
Через 5 минут стартанет прямой эфир Research Insights Made Simple, где мы вместе с Антоном Костериным, principal engineer RnD-центра Т-Банка, разберём свежий материал Anthropic — The AI-Native SDLC playbook. С Антоном мы уже говорили об architecture governance, RFC/ADR и архитектурных ревью. Теперь вопрос шире…
3 AImigo S1E3: Новостной дайджест AI за август (Рубрика #AI)
В пятницу в 12:00 у нас пройдет последний эфир 3 AImigo в этом августе и мы решили проверить новый формат с обсуждением новостей AI за месяц.
Вообще, тема AI развивается очень бурно и событий, что достойны упоминания достаточно много: новые модели и продукты, исследования, заметные кейсы, изменения в подходах команд к разработке с AI. Мы выбрали новости,…
🔥6👍3❤2
Signed Alexander Polomodov
Showing the 12 most recent of 104 posts we hold for @book_cube. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@book_cube edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
11 August 2026
Most recent edit
15 August 2026
Citation-graph rank
Citation-graph rank — 6,327 of 1,627,068entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 20 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
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.
T-Crew @t_crew · 42,593 Telegram ranks this channel #49 of 95 here — alongside 94 others — read 29 August 2026
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.
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“Книжный куб” (@book_cube), 15,565 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/book_cube.
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.