Разборы книг, статей и докладов про архитектуру, инженерное лидерство и AI в разработке. Каждый день.
Автор: Александр Поломодов (@apolomodov), технический лидер, ex-CTO и Technical Fellow.
YouTube: youtube.com/@TellMeAboutTech
Сайт: polomodov.tech
Created
Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
62 measurements spanning 96 days, net +3,336. 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,172–18,508 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)
Subscribers
Change
10 Nov 2026, 06:47
18,008
+411
8 Nov 2026, 20:52
17,597
+144
7 Nov 2026, 16:57
17,453
+125
6 Nov 2026, 18:25
17,328
+116
5 Nov 2026, 20:00
17,212
+170
4 Nov 2026, 19:56
17,042
+117
3 Nov 2026, 22:16
16,925
+322
2 Nov 2026, 22:15
16,603
+222
1 Nov 2026, 21:10
16,381
+107
1 Nov 2026, 00:06
16,274
+67
30 Oct 2026, 21:27
16,207
+207
29 Oct 2026, 23:37
16,000
+188
29 Oct 2026, 01:07
15,812
-1
27 Oct 2026, 22:00
15,813
+4
26 Oct 2026, 21:47
15,809
+9
25 Oct 2026, 23:27
15,800
+10
24 Oct 2026, 20:08
15,790
+1
23 Oct 2026, 18:08
15,789
-2
22 Oct 2026, 18:38
15,791
+1
21 Oct 2026, 15:55
15,790
first reading
Engagement
165 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 69 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
13.7%
avg views ÷ 18,008 subscribers
Avg views / post
2,480
46 posts measured
Reaction rate
0.633%
reactions ÷ views · ER floor
Posts in window
48
of 165 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 10 November 2026
Posts held
165 (31 July 2026 – 10 November 2026)
Views total
113,890
Reactions total
721
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 04:34 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
≈3,050
Videos
≈6
Links
≈2,610
Lifetime counters from Telegram’s own channel header, read 11 November 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
2,441 reactions across 156 posts, in 34 distinct kinds. The most used accounts for 33.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
810
33.2%
🔥
796
32.6%
👍
640
26.2%
😱
39
1.60%
👎
22
0.901%
🤔
16
0.655%
💔
14
0.574%
😢
13
0.533%
😁
12
0.492%
🫡
12
0.492%
🌚
7
0.287%
🕊
7
0.287%
👾
5
0.205%
💅
5
0.205%
💯
5
0.205%
🤝
5
0.205%
❤🔥
4
0.164%
🗿
4
0.164%
😭
4
0.164%
👌
3
0.123%
14 further kinds
18
0.737%
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 162 of the 165 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 2,570 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 165 most recent posts we hold, published 31 July 2026 to 10 November 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
23
across the posts below
Posts paid on
19
of 163 we hold a reading for · 12%
Most on one post
3
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 165 most recent posts we hold for this entry, published 31 July 2026 to 10 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 7 of 48 posts held from the last 30 days (14.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
[2/2] Когда память одного аналитика пригодится всей команде (Рубрика #Agent)
Продолжая обсуждение MemCurrent от Databrics хочется рассмотреть вопрос применения памяти не только в разрезе пользователя, но и выше.
«Исключай фоновые запросы» - так в примере из статьи аналитик поправляет расчёт активных пользователей. В следующей сессии того же человека тест проверяет, учтёт ли агент этот фильтр в новом отчёте. Когда т…
AGENTS.md / Помогает ли файл контекста агенту? — Research Insights Made Simple
После добавления AGENTS.md агент чаще запускает тесты и читает больше файлов. Но помогает ли это ему решить больше задач?
В новом выпуске Research Insights Made Simple, что выйдет сегодня в прямом эфире в 13:15 я разбираю исследование "Evaluating AGENTS.md". На SWE-bench и CTXbench авторы проверили, как файл инструкций влияет на долю реш…
[1/2] MemCurrent: что агент уносит из прошлой сессии (Рубрика #Agent)
Databricks в октябре описала MemCurrent — систему памяти, которая помогает агенту использовать опыт прошлых сессий. В Genie, где пользователи задают вопросы к своим данным, таким опытом может быть поправка к расчёту метрики, знание о том, какую таблицу брать, или уже проверенный способ связать несколько таблиц.
У MemCurrent два слоя. В одном лежи…
От разработчика до CTO и COO Manychat — материалы выпуска (Рубрика #Management)
8 ноября вышел мой разговор с Димой Кушниковым, CTO и COO Manychat (Code of Leadership, S2E30, выпуск № 88). К моменту прихода в Manychat Дима уже успел побыть CTO в стартапе. И тут он откликнулся на вакансию бэкенд-разработчика: хотел снова писать код и разобраться, как устроен продукт в небольшой компании. Потом в Manychat он возглавил…
Снятся ли агентам электроовцы? Как Claude пересматривает свою память (Рубрика #AI)
Когда в статье Anthropic "The components of agent memory" дошёл до слова dreaming, сразу вспомнил одну из своих любимых книг "Do Androids Dream of Electric Sheep?" Филипа Дика. В «Книжном кубе» я уже вспоминал этот роман, когда рассказывал про биографию Дика в комиксах и артбук по «Бегущему по лезвию 2049». А тут у «снов» нашлась инже…
Gitleaks и секреты, которые помнит Git (Рубрика #Software)
Рюкзак и кружка. Зак Райс вспоминает, как получил такой фидбэк от австралийской консалтинговой фирмы ещё до выхода Gitleaks 1.0. К подаркам прилагалось письмо: ребята уже прогоняли через его сканер сотни гигабайт репозиториев. А начиналось всё в 2018 году с экспериментов с Kali Linux после работы и желания выучить Go.
В десятиминутной документалке CultRepo …
[2/2] AI-native организация: от сигнала до действия (Рубрика #Management)
Хочу продолжить мысль про координацию из предыдущего поста про Organizing Intelligence, но на уровне целой компании. Это продолжает идеи и восьмого выпуска 3 AImigo «AI-native: что это значит для компании?», где мы с Алексеем Литвиновым и Евгением Сергеевым обсуждали общий контекст, перестройку процессов и очередь вопросов к человеку. Здесь хо…
[1/2] Organizing Intelligence: экономика координации (Рубрика #AI)
В свежем эссе от 29 октября "The Economics of Intelligence: How and when does AGI lead to economic transformation?" и статье "Organizing Intelligence" меня заинтересовал вопрос: как меняется экономика, когда интеллект можно копировать? Отдельно отмечу, что эссе читать легко, но самая мякотка в whitepaper, который я просмотрел, но пока целиком не проч…
Code of Leadership: как растёт ответственность CTO с Василием Гигаури (Рубрика #Management)
В новом выпуске 17 ноября в 15:00 по Москве — Василий Гигаури, CTO и член правления «Честного знака». За его плечами — работа в Deutsche Bank и BNP Paribas, рост инженерной организации с 200 до 580+ специалистов и технологические изменения в системе национального масштаба.
Поговорим о том, как меняется работа руководителя, к…
«Video.js: The Documentary» и цена поддержки open source (Рубрика #Software)
Что происходит с открытым проектом, когда им пользуется множество команд, а люди, которые его поддерживают, больше не могут этим заниматься? Документалка Cult.Repo про Video.js хорошо показывает сразу несколько вариантов этой проблемы.
В 2010 году Стив Хеффернан за выходные собрал элементы управления для нового HTML5 video и выложил резуль…
❤4👍4🔥1
Signed Alexander Polomodov
Showing the 12 most recent of 165 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.
Posts edited after publishing
@book_cube edited 3 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
7 November 2026
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 23 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.
Код Желтый @kod_zheltyi · 33,560 Telegram ranks this channel #6 of 96 here — alongside 95 others — read 4 September 2026
Инжиниринг Данных @rockyourdata · 23,679 Telegram ranks this channel #11 of 93 here — alongside 92 others — read 17 September 2026
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд @leadgr · 31,685 Telegram ranks this channel #16 of 96 here — alongside 95 others — read 10 September 2026
AvitoTech @avitotech · 25,811 Telegram ranks this channel #24 of 96 here — alongside 95 others — read 14 September 2026
Максим Дорофеев: Прокрастинация и джедайские техники @mnogosdelal · 25,891 Telegram ranks this channel #30 of 97 here — alongside 96 others — read 14 September 2026
Диджитализируй! @t0digital · 28,616 Telegram ranks this channel #34 of 88 here — alongside 87 others — read 9 September 2026
T-Crew @t_crew · 43,532 Telegram ranks this channel #49 of 95 here — alongside 94 others — read 29 August 2026
I’m CTO, bitch @ctobtch · 20,219 Telegram ranks this channel #51 of 95 here — alongside 94 others — read 28 September 2026
Системный Аналитик @sys_sa · 19,111 Telegram ranks this channel #58 of 96 here — alongside 95 others — read 3 October 2026
Нестыдная фасилитация @no_shame_facilitation · 22,556 Telegram ranks this channel #60 of 99 here — alongside 98 others — read 19 September 2026
ИТ-Пикник @IT_picnic · 22,795 Telegram ranks this channel #62 of 94 here — alongside 93 others — read 18 September 2026
getmatch: канал про карьеру в IT @g_jobchannel · 18,988 Telegram ranks this channel #65 of 95 here — alongside 94 others — read 5 October 2026
FEDOR BORSHEV @pmdaily · 23,648 Telegram ranks this channel #69 of 97 here — alongside 96 others — read 17 September 2026
Системный анализ | Ольга Пономарева @system_analyse · 31,168 Telegram ranks this channel #69 of 97 here — alongside 96 others — read 6 September 2026
Yandex for Developers @Yandex4Developers · 28,656 Telegram ranks this channel #71 of 94 here — alongside 93 others — read 9 September 2026
АйТиБорода @itbeard · 19,001 Telegram ranks this channel #72 of 93 here — alongside 92 others — read 3 October 2026
DevOps&SRE Library @devopslibrary · 19,870 Telegram ranks this channel #72 of 94 here — alongside 93 others — read 30 September 2026
Yandex Cloud @yandexcloudnews · 23,951 Telegram ranks this channel #72 of 97 here — alongside 96 others — read 22 September 2026
Профсоюз работников IT @ruitunion · 36,079 Telegram ranks this channel #74 of 94 here — alongside 93 others — read 2 September 2026
GetAnalyst - Навыки • Системный анализ • Бизнес-анализ @getanalysts · 22,707 Telegram ranks this channel #75 of 96 here — alongside 95 others — read 20 September 2026
запуск завтра @ctodaily · 33,711 Telegram ranks this channel #81 of 96 here — alongside 95 others — read 4 September 2026
Лидерская позиция | Андрей Шапенко @leadership_position · 27,486 Telegram ranks this channel #86 of 98 here — alongside 97 others — read 11 September 2026
Ozon Tech @ozon_tech · 30,158 Telegram ranks this channel #89 of 98 here — alongside 97 others — read 8 September 2026
Яндекс нанимает | Вакансии для разработчиков @ya_jobs · 33,152 Telegram ranks this channel #91 of 96 here — alongside 95 others — read 5 September 2026
This channel appears in 24 seed channels' Telegram-generated recommendation lists 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Книжный куб” (@book_cube), 18,008 subscribers as measured 10 November 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.