Как написать стратегию аналитики и зачем она нужна? Ура, я наконец-то закончил эту статью! Писал ее долго, потому что хотел сделать по-настоящему крутой гайд, в который вложил много сил. И теперь с радостью делюсь с вами. Эта статья для тех, кто недавно стал тимлидом или хедом аналитики и чувствует, что пора выйти из режима «просто делаем задачи» и начать думать системно. Перед тем, как ее опубликовать, я искал по…

Channel
RTD: Ссылки и репосты
@rtdlinks
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
572subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001281187831 |
|---|---|
| Type | Channel |
| Username | @rtdlinks |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/rtdlinks |
Topic
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 21 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 03:00 | 572 | -1 |
| 3 Sept 2026, 20:55 | 573 | -2 |
| 21 Aug 2026, 01:29 | 575 | -1 |
| 7 Aug 2026, 11:45 | 576 | no change |
| 6 Aug 2026, 18:34 | 576 | first reading |
Engagement
18 posts held, back to 2 February 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 1 page of 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 18 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
20 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 85.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 85.0% | |
| 🐳 | 2 | 10.0% | |
| 😁 | 1 | 5.00% |
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 7 of the 18 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 2 February 2026 to 15 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.
Recent posts
Microsoft сделал язык Flint для создания графиков и визуализаций через AI-агентов Поддерживает 46 типов диаграмм и рендеринг в Vega-Lite, ECharts и Chart.js. Код открыт. Есть MCP. https://microsoft.github.io/flint-chart/
http://openai.com/index/how-agents-are-transforming-work/
Я спарсил все скилы с гитхаба, кластеризировал и прогнал по эвалам. Результаты: - 1 из 3 скилов делает задачу хуже, чем без скила - звездочки вообще не показатель - чем хуже модель, тем полезнее скилы
👍2
🏁 Аналитика без аналитика: как Anthropic дошёл до 95% Многим начинающим аналитикам рано или поздно на уровне целей и ориентиров продают историю о self-service аналитике – чтобы продакт сам получал ответы на свои вопросы через аналитические инструменты Раньше это в основном было в контексте дэшбордов – сделать их и научить продактов ими пользоваться. Год-два назад на конференциях начали рассказывать про мечту о text…
👍5🐳2
Microsoft опенсорснули проект SkillOpt для оптимизации способностей агентов Это фреймворк, который фоново улучшает вашего агента через изменение markdown файлов со скиллами. Это похоже на классический learning loop, но в текстовом пространстве. То есть агент выполняет задачи с текущей версией условного skill.md (это аналог прямого прохода), система легирует все, что тот делает, отмечает ошибки и успешные ответы, а …
☕️ Агентная аналитика для продактов. Материалы воркшопа Провёл воркшоп у Podlodka ProductCrew — «Агентная аналитика для продактов». Запись уже выложена. Главный тезис: аналитику можно делать на любой модели, не важно какая она. Главное - контекст, который вы ей даёте. Чтобы продемострировать это сделал два публичных репо на одних и тех же данных вымышленного фитнес-приложения: — fitflow-bare — голая БД, никакого к…
Мы видим AI везде, кроме статистики Сегодня обсуждали парадокс, который, имхо, объясняет 90% разочарований от AI. Солоу, нобелевский лауерат по экономике, как-то заметил: Мы видим компьютеры повсюду, только не в показателях производительности Компании массово покупали компьютеры, но производительность не росла. Звучит знакомо? Собственно, тот же парадокс сейчас: Goldman Sachs пишет, что на макроуровне пока нет зн…
👍3
Чем конкретнее задача от заказчика — тем выше шанс, что вы сделаете работу в стол. ————— Да это бред! Метрики понятны, срезы указаны, даже цель ясна — отслеживать активность пользователей. Всё по SMART. Бери и делай, что время терять? Да, только через неделю на демо: «не то хотели», «а где ещё вот это», «руководство просило другое». Почему так происходит? Потому что заказчик проделал за вас самую важную работу — п…
👍3😁1
How to. ClickHouse Projections Простой способ ускорить самые популярные метрики и разрезы дэша - проекции. Проекции физически хранят предпосчитанные метрики на диске, за ними не надо следить: они считаются автоматически при обновлении таблички или какой-то партиции, и позволяют вам прилично снизить нагрузку на железо.
exp-tools.ru
Дописал большую статью, которую пытался дописать последние 2 недели 🍺 В ней рассуждения на тему того, как изменится продуктовая разработка после появления инструментов типа Claude Code/Codex и похожих. Просто рассуждать - скучно, поэтому я провел эксперимент по созданию продукта с нуля, немного позалезал внутрь claude code, обвесил телеметрией и замерил - но не все собранное пока переварил, потому что все ожидаемо о…
Showing the 12 most recent of 18 posts we hold for @rtdlinks. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
@think_visualize · 2602 postsEDU
@ProductsAndStartups · 15,3931 postGPT/ChatGPT/AI Central Александра Горного
@aioftheday · 43,8071 postAgentic World
@anti_notes · 1,2081 postfrom:adam
@c3po_notes · 6,0081 poste/acc
@cryptoEssay · 62,5981 postЧерез тернии к Визам
@data2viz · 6941 postData Secrets
@data_secrets · 93,8001 postТагир Анализирует
@tagir_analyzes · 11,7021 postThis is Data
@thisisdata · 6,2051 postДелаю BI
@withdata · 5061 postРаботая в айтишечке
@workinginit · 1,4811 post
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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@rtdlinks named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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.
@analyst_club · 33,554
Telegram ranks this channel #24 of 96 here — alongside 95 others — read 4 September 2026
@revealthedata · 27,839
Telegram ranks this channel #27 of 96 here — alongside 95 others — read 10 September 2026
@nastengraph · 28,213
Telegram ranks this channel #33 of 94 here — alongside 93 others — read 9 September 2026
@leftjoin · 42,064
Telegram ranks this channel #46 of 95 here — alongside 94 others — read 29 August 2026
This channel appears in 4 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“RTD: Ссылки и репосты” (@rtdlinks), 572 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/rtdlinks.
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.