Анонсы новых выпусков, голосования и прочие замечательные инфоповоды от лучшего подкаста про IT.
Манифест выбора гостей и тем: podlodka.io/manifest
SoundCloud: https://soundcloud.com/podlodka
Чат: @podlodka
По всем вопросам: @tanyasanovna
Created
9 December 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
27 measurements spanning 102 days, net +104. 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 7,206–7,370 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
16 Nov 2026, 01:30
7,351
+9
11 Nov 2026, 00:08
7,342
+10
7 Nov 2026, 09:50
7,332
+33
1 Nov 2026, 09:19
7,299
+1
29 Oct 2026, 01:49
7,298
+14
25 Oct 2026, 20:49
7,284
+2
22 Oct 2026, 19:16
7,282
+4
19 Oct 2026, 16:31
7,278
+8
17 Oct 2026, 02:47
7,270
-2
14 Oct 2026, 13:07
7,272
+12
10 Oct 2026, 19:37
7,260
+12
4 Oct 2026, 16:37
7,248
+12
24 Sept 2026, 20:57
7,236
+11
17 Sept 2026, 01:20
7,225
-8
13 Sept 2026, 03:55
7,233
-1
8 Sept 2026, 23:15
7,234
-5
3 Sept 2026, 11:01
7,239
-3
31 Aug 2026, 13:54
7,242
-2
28 Aug 2026, 05:05
7,244
-1
25 Aug 2026, 04:16
7,245
first reading
Engagement
38 posts held, back to 19 May 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 40 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
22.8%
avg views ÷ 7,351 subscribers
Avg views / post
1,670
11 posts measured
Reaction rate
1.21%
reactions ÷ views · ER floor
Posts in window
11
of 38 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 16 November 2026
Posts held
38 (19 May 2026 – 16 November 2026)
Views total
18,400
Reactions total
222
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 20:54 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
≈824
Videos
≈37
Links
≈1,460
Lifetime counters from Telegram’s own channel header, read 17 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.
Video runtime
1m 12s
Average length
1m 12s
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.
Reaction mix
1,141 reactions across 37 posts, in 33 distinct kinds. The most used accounts for 18.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
208
18.2%
❤
187
16.4%
👍
166
14.5%
🤡
147
12.9%
👎
103
9.03%
❤🔥
50
4.38%
🤨
43
3.77%
🥴
40
3.51%
💊
38
3.33%
😁
35
3.07%
💅
34
2.98%
😍
26
2.28%
🤣
19
1.67%
🥱
9
0.789%
👏
4
0.351%
🦄
4
0.351%
😱
3
0.263%
🤔
3
0.263%
🤩
3
0.263%
⚡
2
0.175%
13 further kinds
17
1.49%
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 37 of the 38 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,141 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 19 May 2026 to 16 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.
Advertising
Ad load
18.4%
7 of 38 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
2,170
over 7 measured posts
Median views · rest
2,310
over 31 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2SDnjbocFa3
1
14 July 2026
14 July 2026
2SDnjcXQjbR
1
11 August 2026
11 August 2026
2SDnjdBhcfd
1
27 July 2026
27 July 2026
2SDnjdbfsR5
1
3 August 2026
3 August 2026
2SDnjdsfbtg
1
3 November 2026
3 November 2026
2SDnjeJxBbg
1
11 June 2026
11 June 2026
CQH36pWzJqVL1zRoSyy4zU8Ldi1kNNEYA37vnG5vcbfCRw
1
21 October 2026
21 October 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 38 most recent posts we hold, published 19 May 2026 to 16 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) 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).
Podlodka #503 – Агентская инфраструктура
В теории агентская разработка может многократно увеличить продуктивность команд. На практике вместе с количеством агентов растут и стоимость, и сложность, и количество рисков. Более того, недостаточно просто дать командам запускать агентов. Их эффективность напрямую зависит от того, к какому контексту компании они будут иметь доступ. Мы позвали Павла Агалецкого из Авито, чтоб…
Бреслав и Ложечкин #43 — Почему всё так медленно?
Поговорили про скорость. Почему всё всегда так медленно? Что мешает двигаться быстрее? А когда, наоборот, лучше помедленнее? Выпуск развивает тему сложности из выпуска 41.
Слушать выпуск:
Telegram
Mave
Apple
Castbox
Spotify
YouTube.Music
YouTube
Podlodka #502 – Ассемблер
«Никогда не программируйте на ассемблере» – первое правило Константина Владимирова, преподавателя МФТИ и автора курса по C и ассемблеру, но зачем тогда разработчику уметь его читать? Представьте, что в дебаге программа работает, а в релизе падает при чтении из памяти. В отладчике можно проследить, как программа вычислила адрес, по которому попыталась прочитать данные.
В выпуске разбираем, …
🔍 QA в эпоху AI: свежие кейсы на Podlodka QA Crew
Совсем скоро стартует новый сезон Podlodka QA Crew — с 16 по 20 ноября будем говорить про QA в эпоху AI.
Мы собрали практиков, которые уже активно внедряют агентов в реальные процессы и готовы поделиться не только интересными находками, но и ограничениями, ошибками и неочевидными выводами.
🧠 В этом сезоне:
• Разберёмся, как онбордить ИИ-агента в проект, настраиват…
Podlodka #501 – Локальные модели для кодинга
Подписка на облачного кодинг-агента стоит не так уж дорого. Зачем тогда покупать GPU и запускать модель самому? Вместе с Иваном Опариным из Wildberries разбираемся, какие локальные модели уже годятся для агентной разработки, где они уступают облачным, сколько стоит железо под них и как настраивать их под свою кодовую базу.
А самое главное – дадим подробный гайд по тому, …
💸 Во что продакты инвестируют ресурсы в кризис?
Когда бюджеты ограничены, цена каждого решения растёт.
• Какие расходы можно сократить без ущерба для продукта?
• Где AI помогает экономить, а на что не стоит тратить токены?
• И как находить новые источники роста, когда привычные подходы перестают работать?
Уже 9 ноября стартует Podlodka Product Crew — «Экономика продукта в кризис».
Что унесёте с конференции:
🔎 По…
Что теперь тестируют QA-инженеры? Разбираемся на Podlodka QA Crew
Этой осенью мы разбирались, как AI меняет индустрию и нас вместе с ней. Собирали новые подходы и практики: от работы с серверной частью до нюансов фронтенда, от формирования видения продукта до пересборки команд.
Осталась ещё одна важная тема — QA в эпоху AI. Новый сезон стартует 16 ноября👇
В тестировании AI влияет не только на скорость процессов, н…
Podlodka #500 – Будущее разработки
500 выпусков и девять с половиной лет разговоров про IT – пора проверить, какие из наших убеждений ещё работают. Собрались полным составом, похвастались навайбкоженными проектами и обсудили, как AI изменил нашу собственную работу. Отдельно поспорили о судьбе инди-хакинга: как меняется создание собственных продуктов, когда код можно поручить агенту, и стоит ли ждать волны независимы…
💸 Экономика продукта в кризис — новый сезон Podlodka Product Crew
Рынок штормит: пользователи осторожнее тратят деньги, бюджеты на развитие продуктов сокращаются, а бизнес всё настойчивее требует снижать издержки — в том числе с помощью AI.
В итоге продактам нужно постоянно находить точки роста в условиях, когда стандартных инструментов уже недостаточно.
С 9 ноября стартует новый сезон Podlodka Product Crew — «Эко…
Когда языковые модели всё больше используются в рабочих задачах, появляются максимально практические вопросы: сколько стоят запросы, как подключить фронтирные модели и как всё это оплачивать.
CheapGPT предлагает собрать это в одном сервисе: единый API к GPT, Claude и Gemini, привычные SDK и оплату в рублях. По данным команды, цены ниже, чем у провайдеров: GPT-6.1 Sol обходится примерно втрое дешевле, а Claude на 40%…
👨🏻💻 AI в бэкенд-задачах — на Podlodka Backend Crew
Уже 26 октября мы ждём бэкендеров на Podlodka Backend Crew, чтобы вместе разобрать то, что происходит после того, как AI написал код.
В программе сезона нет докладов в жанре «у нас все получилось». Только реальная практика, сложные случаи и ограничения, с которыми мы сталкиваемся сегодня.
🗓 С 26 по 30 октября:
• Разберём пулл‑реквесты от агента и попробуем пред…
Мы организуем новый хакатон
В нашем AI клубе на днях стартует новый хакатон – будем делать самообучающихся агентов. Идея примерно такая:
👉Берете какой-то поток однотипных задач – например, разбор входящих крешей или обновление документации.
👉Собираете агента или скилл, который умеет эти задачи обрабатывать.
👉Сохраняете в отдельную внешнюю память все, что в этом процессе идет не так – ошибки, комментарии человека, ф…
👎35🥱6❤4👌1👍1
Signed Egor Tolstoy
Showing the 12 most recent of 38 posts we hold for @podlodkanews. 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
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 7 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.
Teamlead Good Reads – ежедневные советы про менеджмент людей и команд @leadgr · 32,538 Telegram ranks this channel #32 of 96 here — alongside 95 others — read 10 September 2026
AvitoTech @avitotech · 25,824 Telegram ranks this channel #47 of 96 here — alongside 95 others — read 14 September 2026
FEDOR BORSHEV @pmdaily · 23,591 Telegram ranks this channel #56 of 97 here — alongside 96 others — read 17 September 2026
Yandex for Developers @Yandex4Developers · 28,673 Telegram ranks this channel #58 of 94 here — alongside 93 others — read 9 September 2026
Код Желтый @kod_zheltyi · 33,570 Telegram ranks this channel #68 of 96 here — alongside 95 others — read 4 September 2026
Нестыдная фасилитация @no_shame_facilitation · 22,526 Telegram ranks this channel #76 of 99 here — alongside 98 others — read 19 September 2026
Максим Дорофеев: Прокрастинация и джедайские техники @mnogosdelal · 25,873 Telegram ranks this channel #94 of 97 here — alongside 96 others — read 14 September 2026
This channel appears in 7 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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“Podlodka Podcast – анонсы и новости подкаста про IT” (@podlodkanews), 7,351 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/podlodkanews.
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.