Telegram RegisterThe public register of Telegram
Telegram profile photo for AI-Driven Development. Родион Мостовой

Channel

AI-Driven Development. Родион Мостовой

@ai_driven

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

7,655subscribers

+2,342 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002040323909
TypeChannel
Username@ai_driven
DescriptionУвлекательно рассказываю о моем опыте применения AI в разработке и построении продуктов с LLM под капотом. Связь: @rodion_m_tg Чат: @ai_driven_chat
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/ai_driven

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 13 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

5,3107,6556,482.56 August 2026 — 5,313 subscribers6 August 2026 — 5,313 subscribers9 August 2026 — 5,310 subscribers12 August 2026 — 5,312 subscribers15 August 2026 — 5,313 subscribers18 August 2026 — 5,314 subscribers24 August 2026 — 5,313 subscribers27 August 2026 — 5,311 subscribers7 September 2026 — 5,321 subscribers11 September 2026 — 5,324 subscribers15 September 2026 — 5,337 subscribers27 September 2026 — 5,492 subscribers5 October 2026 — 5,507 subscribers12 October 2026 — 5,578 subscribers15 October 2026 — 5,621 subscribers18 October 2026 — 5,628 subscribers21 October 2026 — 5,633 subscribers24 October 2026 — 5,630 subscribers27 October 2026 — 5,627 subscribers30 October 2026 — 6,294 subscribers2 November 2026 — 6,634 subscribers5 November 2026 — 7,131 subscribers9 November 2026 — 7,655 subscribers6 August 20269 November 2026
23 measurements spanning 95 days, net +2,342. 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 4,958–8,007 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
9 Nov 2026, 11:467,655+524
5 Nov 2026, 20:017,131+497
2 Nov 2026, 16:296,634+340
30 Oct 2026, 09:286,294+667
27 Oct 2026, 15:165,627-3
24 Oct 2026, 04:365,630-3
21 Oct 2026, 10:195,633+5
18 Oct 2026, 04:585,628+7
15 Oct 2026, 13:495,621+43
12 Oct 2026, 09:025,578+71
5 Oct 2026, 09:365,507+15
27 Sept 2026, 00:575,492+155
15 Sept 2026, 07:215,337+13
11 Sept 2026, 11:575,324+3
7 Sept 2026, 01:425,321+10
27 Aug 2026, 11:445,311-2
24 Aug 2026, 09:065,313-1
18 Aug 2026, 12:045,314+1
15 Aug 2026, 20:175,313+1
12 Aug 2026, 14:155,312first reading

Engagement

37 posts held, back to 8 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 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
55.1%
avg views ÷ 7,655 subscribers
Avg views / post
4,220
2 posts measured
Reaction rate
0.617%
reactions ÷ views · ER floor
Posts in window
2
of 37 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
WindowRolling 30 days · latest post in window 30 October 2026
Posts held37 (8 July 2026 – 30 October 2026)
Views total8,430
Reactions total52
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 20:51 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
140
Videos
4
Links
165

Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
10s
Average length
10s

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

878 reactions across 36 posts, in 10 distinct kinds. The most used accounts for 52.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍45752.1%
❤21624.6%
😁768.66%
🤯333.76%
🔥262.96%
🤔262.96%
🎉171.94%
👎171.94%
🦄80.911%
💯20.228%

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 36 of the 37 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 878 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 37 most recent posts we hold, published 8 July 2026 to 30 October 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
17
across the posts below
Posts paid on
10
of 37 we hold a reading for · 27%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ai_driven. 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 37 most recent posts we hold for this entry, published 8 July 2026 to 30 October 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: 1 of 2 posts held from the last 30 days (50.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).

30 Oct 2026, 14:11 UTC≈4,720 views8 reactionsread 10 November 2026

Бекдор в Claude Code расширении для VSCode/Cursor TL;DR - недавнюю версию Claude Code extension for VSCode/Cursor/etc. атаковали бекдором через одну из его зависимостей (пресловутый supply chain), поэтому стоит проверить не попал ли ваш ПК под атаку - проверить можно через своего агента Cursor говорят, что сервер атакующего уже отключен, но если ваш ПК таки попал под атаку, то стоит как минимум отозвать ключи из .e…

👍4🤔4

28 Oct 2026, 15:49 UTC≈3,710 views44 reactionsread 10 November 2026
Photo

Выхожу из сумрака, чтобы разом рассказать на новой конфе все то, о чем не успеваю рассказать в канале. Мы собрали самых топовых руссоязычных спикеров в сфере агентной разработки (до кого смогли дотянуть) и организовали с ними конфу. Помимо оркестрации команды агентов, я впервые структурировано расскажу про свой агентный сетап, про свои подходы, уникальные скиллы, а также почему я ушел от Spec-Driven фреймворков и даж…

🔥26❤12👍6

6 Oct 2026, 15:10 UTC≈4,010 views30 reactionsread 10 November 2026

Собеседования на программиста в эпоху AI Помните раньше была такая штука как собеседование по теории? Когда просто задают вопросы а-ля "как работает хеш таблица" или "а что там происходит при коллизиях"? Так вот, оказывается, такое и сейчас есть. Вообще, тема собеседований мне весьма не чужда, я даже когда-то готовил людей к прохождению этих самых собеседований, причем весьма успешно. Так вот, формат таких теоретич…

👍18❤9💯2😁1

2 Oct 2026, 07:11 UTC≈9,480 views23 reactionsread 10 November 2026

Онбординг агентов в Enterprise кодовые базы на миллионы LoC Вместе с Максимом Ключниковым (Этихлид) поделились своим опытом о том, как добиться максимум эффективности от AI агентов на больших легаси проектах. Я рассказывал про построение тезауруса и борьбу с тех долгом, а также поделился неочевидными результатами наших бенчмарков, измеряющих эффективность контекстных движков (векторный RAG, графовый RAG). Во второй …

👍17❤5🎉1

27 Sept 2026, 07:05 UTC≈4,250 views23 reactionsread 10 November 2026

Vibe-Observability и автономный баг-фиксинг Эксперементирую с автономным исправлением багов через агента - BugSink тригерит облачный claude code в момент когда возникает эксепшн, тот просыпается ищет причину и исправляет (у него полный ридонли доступ к проду + доступ к репозиторию). Проект эксперимельный, цена ошибки не велика, поэтому такая автономия допустима. Но главное другое - чтобы это все нормально работало,…

❤14👍8🤯1

22 Sept 2026, 12:56 UTC≈3,280 views18 reactionsread 10 November 2026
Forwarded from @kdoronin_blogPhoto

Выступление за выступлением. Примерно так проходит для меня сентябрь. Много знакомств, интересных историй и опыта о том, что работает, а что нет. Вот вам ещё немного анонсов выступлений на грядущую неделю. Во вторник, 22 сентября, в 18:00 (GMT+3) на буткемпе от NAITION расскажу про feedback-loop в работе с агентами. Как правильно настроенные циклы обратной связи помогают достичь более качественного результата от …

👍11❤7

22 Sept 2026, 07:05 UTC≈3,360 views26 reactionsread 10 November 2026
Photo

Чем мой оркестратор отличается от claude -p и т. п.? Помимо полезных инструкций, вправляющих мозги как координатору, так и воркерам, важнейшая фишка конкретно моего pragmatic-orchestration в том, что он умеет перенаправлять воркера прямо во время работы (в Codex эта фича называется Steer). То есть, если агент-координатор во время очередной проверки видит, что условный Devin пошел не туда или что-то не учел, ну или п…

❤20👍3🤔3

21 Sept 2026, 20:21 UTC≈2,920 views29 reactions1 Starread 10 November 2026
Photo

Вот за что люблю очередь сообщений в Codex. Накидываешь задачи на ночь одну за другой и со спокойной душой идешь спать. Спека дошлифовывается, а Девин субагенты потом идут ее выполнять под контролем Астры. Вообще, тщательное разжевывание сложных и неочевидных мест прямо в плане сильной моделью - важнейшая штука в SDD, особенно когда сама работа делегируется агенту подешевле. А планеров в данном случае двое - Астра ос…

👍25❤2🤯1🦄1

18 Sept 2026, 18:50 UTC≈4,450 views42 reactions3 Starsread 10 November 2026

Ребят, на всякий случай уточню для тех, кто не вчитался - по 20$ подписке до 10 октября Девин дают практически бесконечную квоту на свою новую фронтир модель SWE 2.0 - это тюн и без того очень удачной модели Kimi K3. И это пока лучшая модель-исполнитель из тех, что мне встречались - я думаю, на уровне с Sol. У К3, кстати, изначально очень хорошо с удержанием контекста на длинных дистанциях. Я напомню, что Devin недав…

👍30🎉8❤4

18 Sept 2026, 13:17 UTC≈3,510 views56 reactions1 Starread 10 November 2026

Posted without readable text

👍31❤17🤔4🦄3🎉1

18 Sept 2026, 11:13 UTC≈2,420 views14 reactionsread 10 November 2026

Вижу, что кейс с модерацией через Jev актуален, поэтому публикую пример реализации такого Jev-модератора для для Mastra фреймворка. Реализовано в виде кастомного InputProcessor (по аналогии с обычным LLMным ModerationProcessor): https://github.com/CodeAlive-AI/mastra-jev-moderation И мнение Рефата про Jev тоже рекомендую к прочтению: https://t.me/nobilix/303 Кстати, моделька уже появилась на OpenRouter: https://ope…

❤7👍7

18 Sept 2026, 06:50 UTC≈3,020 views36 reactions1 Starread 10 November 2026
Photo

Юзкейсы Jev: улучшение RAG, Browser Use, ... Вы, наверное, уже видели, что появилась новая интересная LLMка Jev - суть ее в том, что она умеет, прежде всего, выбирать правильный вариант ответа (Choice), ну или бинарно отвечать на запрос (Noul) и показывать вероятности каждого варианта. В принципе, современные LLM тоже такое умеют через structured output, но ключевая фишка Jev в том, что делает она это очень быстро и…

👍22❤12👎2

Showing the 12 most recent of 37 posts we hold for @ai_driven. 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.

Forward network

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 25 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“AI-Driven Development. Родион Мостовой” (@ai_driven), 7,655 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/ai_driven.

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.