Telegram RegisterThe public register of Telegram
Telegram profile photo for Записки CTO про код и карьеру

Channel

Записки CTO про код и карьеру

@cto_notes_panov

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

1,064subscribers

+16 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002074942651
TypeChannel
Username@cto_notes_panov
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 live26 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/cto_notes_panov

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

1,0481,0641,0566 August 2026 — 1,048 subscribers6 August 2026 — 1,048 subscribers9 August 2026 — 1,050 subscribers12 August 2026 — 1,052 subscribers15 August 2026 — 1,054 subscribers18 August 2026 — 1,055 subscribers22 August 2026 — 1,057 subscribers28 August 2026 — 1,061 subscribers31 August 2026 — 1,059 subscribers3 September 2026 — 1,057 subscribers9 September 2026 — 1,059 subscribers26 September 2026 — 1,064 subscribers6 August 202626 September 2026
12 measurements spanning 51 days, net +16. 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 1,046–1,066 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 06:571,064+5
9 Sept 2026, 08:391,059+2
3 Sept 2026, 16:011,057-2
31 Aug 2026, 00:031,059-2
28 Aug 2026, 01:131,061+4
22 Aug 2026, 12:421,057+2
18 Aug 2026, 23:261,055+1
15 Aug 2026, 19:561,054+2
12 Aug 2026, 13:161,052+2
9 Aug 2026, 05:521,050+2
6 Aug 2026, 12:511,048no change
6 Aug 2026, 05:211,048first reading

Engagement

20 posts held, back to 5 March 2025 — 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 20 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

506 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 42.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥21442.3%
👍19538.5%
❤8015.8%
⚡50.988%
❤‍🔥40.791%
👏30.593%
💯30.593%
✍10.198%
🤔10.198%

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

Measured over the 20 most recent posts we hold, published 5 March 2025 to 9 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

9 Jul 2026, 09:28 UTC749 views30 reactionsread 6 August 2026

Я выложил свои скиллы для ведения базы знаний в опенсорс В прошлом посте я рассказывал, как перепоручил ведение базы знаний AI-агенту — собрал персональную LLM Wiki по мотивам заметки Андрея Карпати. Меня попросили поделиться навыками. Выкладываю. Репозиторий: github.com/anatoly-tech/obsidian-skills Внутри тири навыка: - compile — разбирает сырые источники из inbox/ в атомарные заметки, строит связи, обновляет MOC…

🔥30

12 Jun 2026, 17:22 UTC≈1,140 views36 reactionsread 6 August 2026

Как я перепоручил ведение базы знаний AI-агенту Я уже довольно давно веду свою базу знаний в Obsidian. И как у любого уважающего себя «хомяка», у меня накопился запас необработанных материалов. Репосты и ссылки из любимых каналов в телеграме, ссылки «прочитать» в to-do листе, рекомендации книг, которые некогда разобрать. Пару месяцев назад вышла нашумевшая статья Андрея Карпати про LLM Wiki. Я давно думал, как испо…

👍27🔥8❤1

1 May 2026, 19:21 UTC≈1,420 views11 reactionsread 6 August 2026

Пост написан по мотивам моего доклада на весеннем Podlodka Teamlead Crew (16 сезон). В докладе раскрыто чуть больше деталей и примеров https://www.youtube.com/watch?v=DADogPVo0CI

👍5❤‍🔥4🔥2

1 May 2026, 19:19 UTC788 viewsread 6 August 2026

И последний пост из серии, про одну из самых сложных задач руководителя - приоритизацию.

1 May 2026, 19:19 UTC≈1,160 views14 reactionsread 6 August 2026
Forwarded from @yandexforteamleadsPhoto

👀 Как переводить инженерные идеи на язык бизнеса Ситуация: приходишь к продакту с идеей рефакторинга, автотестов или quality gates. Кажется, всё логично: багов будет меньше, код улучшится, жить станет веселее. А в ответ: «Не сейчас». Знакомо? Часто так бывает из-за того, что разработка объясняет задачу на техническом языке, а продукт принимает решения на бизнесовом — через эффект, метрики и приоритеты. В какой-то …

👍9❤5

24 Apr 2026, 12:35 UTC771 viewsread 6 August 2026

Второй пост о том, что делать, когда мы уже сняли всю неопределеность и надо наконец-то что-то запланировать и поставить себе и команде цели.

24 Apr 2026, 12:35 UTC936 views7 reactionsread 6 August 2026
Forwarded from @yandexforteamleadsPhoto

💡 Как превратить сырую идею в понятную цель Когда долго работаешь над одним продуктом, идеи начинают копиться сами собой. Хочется исправить баги в одном месте, попробовать AI для разработки в другом, отрефакторить легаси, вынести что-то из монолита в микросервисы и поднять автоматизацию тестирования. И в этот момент легко попасть в ловушку «ну тут же и так всё понятно, просто делаем». Проблема в том, что такой спис…

👍6❤1

23 Apr 2026, 06:48 UTC823 views21 reactionsread 6 August 2026
Forwarded from @yandexforteamleadsPhoto

📎 Как действовать в условиях неопределённости Всем привет! На связи Толя Панов, CTO Яндекс Карт и админ Yandex for Teamleads на этой неделе. Допустим, вам нужно принять важное решение, которое повлияет на развитие продукта. В такой ситуации хочется учесть все риски и возможные сценарии, но в 2026 году рассчитывать на полностью предсказуемое будущее уже не приходится. В этот момент кажется, что надо ещё посчитать, д…

🔥9👍7❤5

23 Apr 2026, 06:48 UTC765 views0 reactionsread 6 August 2026

На этой неделе я веду тим лидскую колонку в канале @Yandex4Teamleads. Буду делиться с вами репостами от туда 🙂 Встречайте первый пост Как действовать в условиях неопределённости

21 Mar 2026, 06:34 UTC≈1,680 views40 reactionsread 6 August 2026
Photo

28 марта буду на Dream Teamlead. Это практическая конференция Яндекса для тимлидов, руководителей и технических лидеров — про управление людьми, сложные решения и развитие команд. Я буду участвовать в круглом столе «За кулисами кода: один день из жизни руководителя разработки». Поговорим о том, что на самом деле стоит за работой CTO: как выглядит рабочий день, как расставляются приоритеты, как устроена работа со ст…

🔥24❤10👍6

6 Mar 2026, 15:05 UTC≈1,770 views58 reactionsread 6 August 2026

Почему изменения в больших командах буксуют Прочитал пост Жени Антонова про внедрение новых процессов. Женя пишет, что процессы можно внедрять: 1. директивно — с поддержкой административного ресурса руководителя. Обычно это проще и быстрее. 2. через вовлечение людей — нужно создать у них потребность и убедить, что изменения им полезны. Мысль абсолютно верная. Но на практике для больших команд такие чёрно-белые схе…

❤30🔥20👍7🤔1

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

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.

AvitoTech
@avitotech · 25,625
Telegram ranks this channel #74 of 96 here — alongside 95 others — read 14 September 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“Записки CTO про код и карьеру” (@cto_notes_panov), 1,064 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/cto_notes_panov.

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.