Telegram RegisterThe public register of Telegram
Telegram profile photo for Тимур Хахалев про AI Coding

Channel

Тимур Хахалев про AI Coding

@the_ai_architect

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

13,052subscribers

+4,084 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002293112404
TypeChannel
Username@the_ai_architect
DescriptionАвторский канал. Пишу, помогаю, обучаю, внедряю, консультирую по AI Coding О канале https://t.me/the_ai_architect/2 Связь через ЛС канала | Визитка: timurkhakhalev.t.me
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held34
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/the_ai_architect

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 11 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 the other topics.

Growth

8,96313,05211,007.56 August 2026 — 8,968 subscribers6 August 2026 — 8,968 subscribers6 August 2026 — 8,969 subscribers9 August 2026 — 8,963 subscribers12 August 2026 — 8,982 subscribers15 August 2026 — 8,989 subscribers18 August 2026 — 8,995 subscribers22 August 2026 — 9,012 subscribers25 August 2026 — 9,017 subscribers28 August 2026 — 9,032 subscribers31 August 2026 — 9,034 subscribers3 September 2026 — 9,102 subscribers8 September 2026 — 9,129 subscribers12 September 2026 — 9,176 subscribers16 September 2026 — 9,206 subscribers30 September 2026 — 9,300 subscribers7 October 2026 — 9,374 subscribers13 October 2026 — 9,417 subscribers16 October 2026 — 9,415 subscribers19 October 2026 — 9,403 subscribers23 October 2026 — 9,411 subscribers25 October 2026 — 9,447 subscribers28 October 2026 — 9,833 subscribers31 October 2026 — 10,225 subscribers1 November 2026 — 10,263 subscribers2 November 2026 — 10,444 subscribers3 November 2026 — 10,628 subscribers4 November 2026 — 10,737 subscribers5 November 2026 — 10,830 subscribers6 November 2026 — 10,987 subscribers7 November 2026 — 11,081 subscribers8 November 2026 — 11,163 subscribers10 November 2026 — 11,707 subscribers12 November 2026 — 13,052 subscribers6 August 202612 November 2026
34 measurements spanning 98 days, net +4,084. 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 8,350–13,665 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
12 Nov 2026, 10:1713,052+1,345
10 Nov 2026, 08:4711,707+544
8 Nov 2026, 18:5911,163+82
7 Nov 2026, 10:1511,081+94
6 Nov 2026, 12:2810,987+157
5 Nov 2026, 11:0710,830+93
4 Nov 2026, 12:3610,737+109
3 Nov 2026, 12:3110,628+184
2 Nov 2026, 15:4910,444+181
1 Nov 2026, 16:0010,263+38
31 Oct 2026, 13:5410,225+392
28 Oct 2026, 21:109,833+386
25 Oct 2026, 14:519,447+36
23 Oct 2026, 00:069,411+8
19 Oct 2026, 21:469,403-12
16 Oct 2026, 20:089,415-2
13 Oct 2026, 11:379,417+43
7 Oct 2026, 14:219,374+74
30 Sept 2026, 19:369,300+94
16 Sept 2026, 04:379,206first reading

Engagement

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

ERR · 30 days
41.2%
avg views ÷ 13,052 subscribers
Avg views / post
5,380
25 posts measured
Reaction rate
0.84%
reactions ÷ views · ER floor
Posts in window
26
of 68 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 14 November 2026
Posts held68 (21 July 2026 – 14 November 2026)
Views total134,530
Reactions total1,130
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 10:34 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
109
Videos
23
Links
327

Lifetime counters from Telegram’s own channel header, read 15 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
3m 24s
Average length
1m 08s

Measured directly from 3 videos 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

2,388 reactions across 64 posts, in 11 distinct kinds. The most used accounts for 28.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥67228.1%
❤65627.5%
👍57023.9%
😁25410.6%
👎923.85%
💯622.60%
🌚522.18%
👏120.503%
🎉80.335%
✍70.293%
😭30.126%

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

Measured over the 68 most recent posts we hold, published 21 July 2026 to 14 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
7
of 67 we hold a reading for · 10%
Most on one post
11
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @the_ai_architect. 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 68 most recent posts we hold for this entry, published 21 July 2026 to 14 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: 10 of 26 posts held from the last 30 days (38.5%) 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).

14 Nov 2026, 07:02 UTC≈3,410 views38 reactionsread 15 November 2026

Вы пробовали составлять генеалогическое древо? А с агентами? Я – да. По одной ветке семьи удалось копнуть вплоть до 18 века, я офигел! Есть вот такой skill для того чтобы это делали агенты: https://github.com/DenisSergeevitch/ex-ussr-kinship-research Узнал про него на канале у Артёма Круглова. И сегодня, кстати, мы проведём стрим с Артёмом и его братом Ильёй (старожилы ру ai коммьюнити наверняка его встречали в ч…

🔥22❤9👍4✍3

10 Nov 2026, 13:38 UTC≈6,310 views44 reactionsread 15 November 2026

Для новоприбывших на канал, расскажу кто я Тимур Хахалев – практик, AI энтузиаст, спикер на конференциях, член программного комитета Agentic Dev Conf, AI Native Conf, AI Dev Live. Раннее я был бэкендером (когда работал в найме 😄), теперь я развиваю свои проекты – этот телеграм канал, курс AI Coding для Разрабов: Advanced, и ещё один стелс-проект, про который расскажу подробнее позже, а так же делаю консалтинг по AI…

🔥26❤9👍7✍1🌚1

9 Nov 2026, 16:29 UTC≈5,470 views30 reactionsread 15 November 2026
Photo

Парочка сниппетов из моего выступления 12 ноября на нашей конфе AI Dev Live 2026 Как вкатиться в разработку с ИИ и не выгореть Тезисы: - SDD вам не нужОн - пытаться применить все модные buzzwords в своём проекте – ошибка Как делать правильно: 1. Практика 2. Практика 3. Практика (там конечно есть остальные пункты 😁, но практика это главное) Ну и разберу свой Agentic SDLC Roadmap. Не забудьте зарегистрироваться: …

❤16🔥7👍4😁3

7 Nov 2026, 15:22 UTC≈5,270 views64 reactionsread 15 November 2026

Разраб, который владеет Claude, получает столько же, сколько тот, кто не владеет. И это плохая новость для обоих Для второго всё понятно, про него ниже. А вот почему это плохо для первого, многие пока не замечают. Многие компании сейчас переживают непростые времена. Кто-то ужимается и сокращает расходы, кто-то увольняет людей, а кто-то закрывается. При этом AI агентов так или иначе пытаются использовать уже почти …

🌚29❤16😁9👍7🔥3

6 Nov 2026, 14:08 UTC≈4,700 views35 reactionsread 15 November 2026

Забыл вчера рассказать – я ж ещё Cap.so форкнул. Проблема В сети много инструментов для записи скринкаста со своим лицом с вебки. Есть платные, есть бесплатные. Для первого потока я использовал OBS Studio с плагином, который снимает поток одновременно с нескольких источников: мой экран и вебка. В целом, это работало, но нужно было делать очень много приседаний с настройкой. Да ещё и кастомайзинга формы кадра с ве…

👍20🔥10❤5

5 Nov 2026, 14:16 UTC≈4,470 views51 reactions1 Starread 15 November 2026

Монтаж видео Одной из самых больших болей при выпуске видео контента для меня всегда был монтаж видео. У меня бывают прикольные идеи, но как вспомню, что чтоб выпустить один часовой видос, нужно просидеть пару дней над монтажом в видеоредакторе, то всякое желание что-то записывать отпадает. Первый поток курса Первый поток курса я даже отдавал в работу монтажеру. ("даже" тут стоит, потому что всё остальное я делаю …

🔥30👍14❤7

5 Nov 2026, 08:58 UTC≈3,570 views10 reactionsread 15 November 2026

Отзыв моего ученика 👇 Кстати, рекомендую подписаться на его ещё пока что нишевый канал. Владимир пишет о своём опыте работы с AI агентами. А для тех, кто планировал приобрести мой курс, напоминаю, что курс стартует уже на следующей неделе, во вторник. Успейте приобрести место, пока их не разобрали!

🔥7❤3

5 Nov 2026, 08:58 UTC≈3,930 views15 reactionsread 15 November 2026

📢 Отзыв и обзор: курс по AI-кодингу Несколько месяцев назад проходил 1й поток "AI Coding для разрабов" Тимура Хахалева. Что тут хочу рассказать: мне было полезно сравнить свою работу с агентами с тем, как похожие задачи решает Тимур. 🏃‍♀️🦀 К этому моменту я уже работал с агентами и пробовал собирать свои пайплайны. Мне было интересно посмотреть, где Тимур обсуждает решение, что оставляет агенту и как проверяет полу…

❤14😁1

3 Nov 2026, 14:13 UTC≈4,530 views44 reactionsread 15 November 2026

Почему агент пишет код быстрее, а вы устаёте сильнее Последние полгода я задаю этот вопрос разработчикам, которые уже работают с агентами. Ответы сводятся к трём болям, у которых один общий корень проблем. Модель и промпты тут ни при чём, про корень расскажу в конце. 1. Всё приходится держать в голове Требования, решения, ограничения проекта. Вы объясняете их агенту, в следующей сессии объясняете снова, и каждый р…

👍16❤15🔥5😁4💯3👏1

3 Nov 2026, 06:45 UTC≈5,150 views71 reactionsread 15 November 2026

Интересные изменения происходят в мире ПО История от Мэтта Безымянный CTO компании с отрицательным денежным потоком обсуждал увольнения. Он говорит: «Не хочу дизморалить, увольнять не буду». Через несколько месяцев рассказывает на подкасте, что у них всё классно и компания зарабатывает больше чем тратит! Как это произошло? - оказалось, компания лицензировала у стороннего вендора компонент, критичный для всего биз…

❤35🔥24👍10🌚1👏1

1 Nov 2026, 17:33 UTC≈6,300 views85 reactions8 Starsread 15 November 2026

Ухожу из найма Почти 5 лет я проработал в аутсорс-компании: мы делали софт на заказ. Начинал backend-разработчиком на Node.js, а со временем занимался уже всем подряд: архитектурой, инфрой, фронтендом, клиентами, процессами, внедрением AI. Последний год мне всё сильнее хотелось заниматься только своими проектами. Работу в компании я перерос, а мои проекты стали приносить ощутимые деньги. Я понимаю, что сейчас не л…

❤34🔥27👍13😁11

1 Nov 2026, 11:02 UTC≈5,050 views17 reactionsread 15 November 2026

Мы с ребятами из тусовочки блоггеров-технарей по AI снова организовываем конфу AI Dev Live! С момента первой конфы прошло уже несколько поколений Claude – 13 месяцев! О чем конфа? О разработке с AI-агентами. Поговорим о текущем состоянии индустрии и о трендах будущего. Год назад мы для нашей аудитории открыли кучу всего интересного и полезного из мира AI, предсказали тренды на 2026й год: - больше llm с 1M контекст…

❤12🔥4😁1

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

Posts edited after publishing

@the_ai_architect edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 November 2026
Most recent edit
12 November 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @the_ai_architect as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
14 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
1

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Jul 2026, 09:51 UTCAnonymous Poll759 voters

Насколько вам удаётся стабильно получать результат с помощью AI Coding?

  1. Пока не пользуюсь2%
  2. Только начинаю5%
  3. Почти всегда получаю нужный результат51%
  4. Обычно получается, но иногда возникают проблемы35%
  5. Часто приходится долго исправлять результат AI7%
  6. Пока AI Coding скорее мешает, чем помогает1%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

23 Jul 2026, 18:11 UTCAnonymous Poll3,290 voters approx.

Мой основной инструмент для AI coding это...

  1. ничем не пользуюсь2%
  2. Codex37%
  3. Claude Code37%
  4. Github Copilot1%
  5. Opencode7%
  6. Cursor8%
  7. chatgpt/claude/deepseek (копирую из чата в IDE и обратно)3%
  8. другое (напишу в комменты)5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 68 most recent posts we hold, published 21 July 2026 to 14 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Тимур Хахалев про AI Coding” (@the_ai_architect), 13,052 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/the_ai_architect.

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.