Telegram RegisterThe public register of Telegram
Telegram profile photo for Этихлид

Channel

Этихлид

@etechlead

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

9,034subscribers

+2,370 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-1002028598037
TypeChannel
Username@etechlead
DescriptionКанал техлида с мыслями об AI, IT и спорте. https://t.me/etechlead/6 - содержание https://t.me/etechlead/8 - о канале https://t.me/+NgQZbosvypEyYWQ6 - чат канала, там отвечаю(т) быстрее :) (без рекламы)
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 held27
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/etechlead

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

6,6649,0347,8496 August 2026 — 6,664 subscribers7 August 2026 — 6,666 subscribers9 August 2026 — 6,676 subscribers12 August 2026 — 6,699 subscribers16 August 2026 — 6,704 subscribers19 August 2026 — 6,723 subscribers22 August 2026 — 6,791 subscribers26 August 2026 — 6,806 subscribers29 August 2026 — 6,817 subscribers1 September 2026 — 6,866 subscribers5 September 2026 — 6,909 subscribers10 September 2026 — 6,932 subscribers14 September 2026 — 6,954 subscribers18 September 2026 — 6,960 subscribers28 September 2026 — 6,985 subscribers5 October 2026 — 6,991 subscribers11 October 2026 — 7,003 subscribers15 October 2026 — 7,000 subscribers18 October 2026 — 6,997 subscribers20 October 2026 — 6,992 subscribers23 October 2026 — 6,996 subscribers26 October 2026 — 6,998 subscribers29 October 2026 — 7,483 subscribers1 November 2026 — 7,772 subscribers3 November 2026 — 8,216 subscribers6 November 2026 — 8,505 subscribers9 November 2026 — 9,034 subscribers6 August 20269 November 2026
27 measurements spanning 96 days, net +2,370. 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 6,309–9,390 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Nov 2026, 17:349,034+529
6 Nov 2026, 10:578,505+289
3 Nov 2026, 20:478,216+444
1 Nov 2026, 02:217,772+289
29 Oct 2026, 12:317,483+485
26 Oct 2026, 01:186,998+2
23 Oct 2026, 11:196,996+4
20 Oct 2026, 21:496,992-5
18 Oct 2026, 03:016,997-3
15 Oct 2026, 07:387,000-3
11 Oct 2026, 23:187,003+12
5 Oct 2026, 18:186,991+6
28 Sept 2026, 01:376,985+25
18 Sept 2026, 11:366,960+6
14 Sept 2026, 12:186,954+22
10 Sept 2026, 21:596,932+23
5 Sept 2026, 19:586,909+43
1 Sept 2026, 12:056,866+49
29 Aug 2026, 02:566,817+11
26 Aug 2026, 02:136,806first reading

Engagement

25 posts held, back to 5 June 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 27 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
57.4%
avg views ÷ 9,034 subscribers
Avg views / post
5,190
4 posts measured
Reaction rate
1.33%
reactions ÷ views · ER floor
Posts in window
4
of 25 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 10 November 2026
Posts held25 (5 June 2026 – 10 November 2026)
Views total20,760
Reactions total276
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 12:32 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
175
Videos
28
Links
163

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. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
15s
Average length
15s

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,474 reactions across 25 posts, in 17 distinct kinds. The most used accounts for 36.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥53536.3%
❤33022.4%
👍32221.8%
😁1298.75%
👏463.12%
🎉432.92%
💯201.36%
❤‍🔥191.29%
✍110.746%
🥱50.339%
🥰40.271%
😱30.204%
👌20.136%
🫡20.136%
🕊10.068%
😢10.068%
🤩10.068%

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

Measured over the 25 most recent posts we hold, published 5 June 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
37
across the posts below
Posts paid on
8
of 25 we hold a reading for · 32%
Most on one post
12
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @etechlead. 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 25 most recent posts we hold for this entry, published 5 June 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: 1 of 4 posts held from the last 30 days (25.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).

10 Nov 2026, 20:24 UTC≈2,960 views49 reactions2 Starsread 11 November 2026
Video

Ну что, уже завтра AI Dev Live 2026 :) Так получилось, что я уже заспойлерил для себя большинство докладов на прогонах. И могу честно сказать: по информационной плотности это, на мой взгляд, одно из лучших мероприятий этого года. При этом спектр тем довольно широк, а точки зрения местами вообще полярные. И это прекрасно: опыт работы с технологиями у людей и компаний сильно разнится, и можно получать результат разны…

🔥29❤9🎉5👍4🥰2

3 Nov 2026, 17:42 UTC≈6,480 views118 reactions1 Starread 11 November 2026
Photo

Моё хобби: экстраполировать :)

😁92🔥14👍5❤4😱3

1 Nov 2026, 17:18 UTC≈5,530 views62 reactions1 Starread 11 November 2026

AI Dev Live 2026 За прошедший год мы увидели, как агенты перестали быть чем-то нишевым и получили весьма широкое распространение в разработке. Да, у всех это выглядит по-разному: кто-то запускает автономные рои и строит самообучающиеся Dark Factories, а кто-то только пробует рискнуть дать агенту сделать git commit. Так или иначе, профессия уже изменилась. Но... как там дела с кукушечкой? Казалось бы, наконец-то м…

🔥28❤18👏7👍6🎉3

13 Oct 2026, 17:40 UTC≈5,790 views47 reactionsread 11 November 2026
Forwarded from @ai_driven

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

🔥19❤17👍5👏4🥰2

22 Sept 2026, 14:49 UTC≈5,860 views40 reactionsread 11 November 2026

Конвертируем Enterprise-проект в Dark Factory Dark Factory - цех без света, потому что людей на линии нет. В разработке это агенты, которые сами доводят задачу до деплоя, а человек ставит цель и принимает результат в контрольных точках. Красиво звучит, когда вас трое и проект свой. А что если он с легаси, без документации, тестов и CI и на нём сменилось несколько поколений разработчиков? Граблей на этом пути предос…

🔥19❤9👍5👏4🎉3

26 Aug 2026, 18:46 UTC≈5,850 views56 reactions12 Starsread 11 November 2026

MAS vs SAS: код писать научились, работать вместе - пока нет (2.2/4) Начало ⬆️ 🔴 Доверие и скепсис пока плохо сбалансированы ● Избыточное доверие: лжец в команде Агент принимает решения по докладам четырёх "скаутов", один из которых систематически врёт. Ложь в принципе обнаружима - доклады пересекаются и рано или поздно противоречат друг другу, но агента при этом никто не предупреждал, что источникам можно не дове…

🔥29👍10❤8✍5🎉4

26 Aug 2026, 18:46 UTC≈3,550 views40 reactionsread 11 November 2026

MAS vs SAS: код писать научились, работать вместе - пока нет (2.1/4) В первой части были очерчены границы: команда агентов окупается там, где задача параллелизуема, и мешает там, где она последовательная. А теперь о том, какие именно командные проблемы появляются, когда агенты всё-таки вынуждены работать вместе? Исследование Anthropic Полнее всего это расписано в работе Patterns and problems in emerging multiagent …

🔥20❤11👍4🎉3❤‍🔥2

25 Aug 2026, 19:53 UTC≈3,810 views89 reactions6 Starsread 11 November 2026

MAS vs SAS: границы применимости (1/4) Мультиагентные системы в целом и для разработки в частности - штука, с которой сообщество агентной инженерии давно экспериментирует, и уже даже вендоры добавляют всякие Agent Teams и Swarms в свои продукты. Однако повсеместным стандартом они до сих пор не стали. Почему? В этой серии постов будем разбираться: 1. Границы применимости - когда хватает одного агента или параллельн…

❤37👍26🔥20👏4🎉2

20 Aug 2026, 16:06 UTC≈3,430 views33 reactionsread 11 November 2026
Forwarded from @kdoronin_blog

Мы начинаем наш стрим "Как писать код с AI-агентами?" Подключайтесь по ссылке: https://youtube.com/live/x0j1kcagoXg

🔥13❤9👍6🥱3🎉2

16 Aug 2026, 16:09 UTC≈3,930 views49 reactionsread 11 November 2026
Forwarded from @kdoronin_blogPhoto

Как писать код с AI-агентами? А если командой? Что нужно учесть, чтобы этот код не положил продакшн? Эти и другие не менее интересные вопросы мы обсудим на следующем стриме на моём YouTube-канале. Для обсуждения я позвал очень интересных гостей: Андрей Бреслав – один из создателей языка программирования Kotlin. Сейчас Андрей разрабатывает Agentic Engineering Toolkit под названием CodeSpeak. Валера Ковальский – …

🔥26❤13👍6🎉2🥱2

8 Aug 2026, 19:39 UTC≈8,610 views98 reactionsread 11 November 2026

The Jeff Dean Facts Из Google после 27 лет работы ушёл Джефф Дин - вместе с несколькими коллегами идёт строить Discovery Loop - стартап про ускорение научных исследований с помощью ИИ. Для меня Джефф - это инженер-легенда и один из тех редких профи, на которых всегда хотелось быть похожим. И не из-за должностей и регалий, а потому, что за ним стоят такие проекты, как Google Search, MapReduce, Bigtable, Protocol Bu…

🔥47😁31👍10❤‍🔥8🫡2

17 Jul 2026, 12:08 UTC≈6,720 views109 reactionsread 11 November 2026

Последний программист Года полтора назад, в одном из постов, я объявлял в розыск рассказ про деда-программиста, который назло всесильному ИИ продолжал писать код руками. Докладываю: рассказ найден, называется "Последний программист", автор - Герберт В. Франке. Публиковался в Компьютерре в 2001м. А до этого ещё и в "Наука и жизнь" в 1990м (ссылки ведут именно на эту версию). А написан он вообще в 1981м! Так вот, и…

❤63🔥29👍14👏2🤩1

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

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

“Этихлид” (@etechlead), 9,034 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/etechlead.

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.