Channel
@TestDrivenChannel
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
71subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001505288573 |
|---|---|
| Type | Channel |
| Username | @TestDrivenChannel |
| Created | 31 August 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 9 times, most recently 10 November 2026 |
| On Telegram | t.me/TestDrivenChannel |
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 28 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @TestDrivenChannel/157 · this entry20 Nov 2023, 09:26 UTC | @MoscowPythonConfChannel/50720 Nov 2023, 09:28 UTC | 1.00 | 72 seconds |
| @TestDrivenChannel/158 · this entry22 Nov 2023, 09:30 UTC | @MoscowPythonConfChannel/50822 Nov 2023, 09:31 UTC | 1.00 | 72 seconds |
| @TestDrivenChannel/159 · this entry24 Nov 2023, 09:51 UTC | @MoscowPythonConfChannel/51024 Nov 2023, 09:52 UTC | 1.00 | under a minute |
| @TestDrivenChannel/162 · this entry25 Dec 2023, 11:09 UTC | @MoscowPythonConfChannel/51325 Dec 2023, 11:10 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @MoscowPythonConfChannel | 5 (5/5 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 29 August 2023 to 29 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @TestDrivenChannel — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 05:35 | 71 | -1 |
| 9 Aug 2026, 22:32 | 72 | no change |
| 6 Aug 2026, 21:31 | 72 | first reading |
20 posts held, back to 29 August 2023 — 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 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
5 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5 | 100.0% |
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 3 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 5 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 29 August 2023 to 29 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.
Компании всё чаще внедряют агентную разработку, но пока сложно понять, насколько широко этот подход используется, какие сценарии действительно работают и с какими сложностями сталкиваются команды. Мы запускаем исследование адаптации агентной разработки и приглашаем вас принять в нём участие. Если в вашей компании уже используют AI-агентов — в разработке, тестировании, ревью кода или других процессах, — расскажите о…
🔥 Олег Бунин побывал в гостях у подкаста «FIDELINA». Получился большой разговор о том, как устроены и куда движутся профессиональные IT-конференции. ✅ Олег рассказал, как меняются конференции в эпоху искусственного интеллекта: про трансформацию формата, организацию мероприятий «под ключ», библиотеку знаний, исследования аудитории и главные ошибки, которые приводят к закрытию даже успешных событий. В выпуске: • как…
👍1
Друзья, поговорим о внедрении AI? Слишком много хайпа вокруг, слишком много инфоцыганства. В YouTube каждая вторая реклама про "Научу вайбкодить доходный бот" :) А давайте используем главный навык наших Программных комитетов, отточенный за десяток лет — отделять реальные работающие решения от хайпа и инфобиза? И применим его к тематике внедрения AI в жизненный цикл разработки. Поговорим на конференциях о качестве …
«Я устал слушать доклады, где всё идеально» «Я уже ничего не внедряю после конференций» «Я не могу услышать опыт компаний, похожих на мою» «Бигтехи говорят на своём языке, а мне это бесполезно» «У меня нет инсайтов — только слайды» Знакомые мысли? Мы это изменим, для этого наша команда придумала новый формат конференций — конференции развития. Конференция развития — инструмент решения задач, а не потребления конте…
👍3
Чтобы принимать верные решения и создавать прорывные продукты, нужно постоянно быть в потоке: знать последние тренды, иметь доступ к лучшим практикам и уметь быстро применять их в работе. Но как успевать за всем? Где брать время на поиск и фильтрацию тонн информации? Представляем вам Поддерживающую базу знаний — ваш персональный пропуск в мир экспертизы для разработчиков, архитекторов и лидеров цифровой индустрии. …
Эта история будет интересна всем, кто использует базы данных. По факту — вообще всем! Ну, может быть кроме пользователей, хотя даже для пользователей вопрос довольно больной. Поэтому не будем пытаться сравнивать разные базы данных, а разберемся, как сейчас эволюционируют и реляционные, и NoSQL, и распределённые базы данных. ⠀ Проблемами развития СУБД поделится директор по продукту в Яндексе. Человек, который отвечает…
🔥 Друзья, не пропустите! 30 ноября и 1 декабря на конференции TeamLead Conf++ 2023 пройдёт открытый трек. Вы сможете посмотреть трансляцию Главного зала конференции бесплатно. Это стало возможным благодаря поддержке нашего генерального партнёра, компании Яндекс. ✅ Чтобы получить доступ к открытому треку, необходимо зарегистрироваться
Андрей Аксёнов нередко начинает свои доклады с такой самопрезентации: «воронежское быдло, интересуюсь информационным поиском». Правда, в Воронеже он уже давно не проживает, но информационный поиск по-прежнему в топе списка его интересов. ⠀ Работает Андрей тимлидом в компании Avito и руководит юнитом инфраструктуры поиска. А ещё именно он создал поисковый движок Sphinx и не ограничился этим, а участвовал ещё во многих…
Кирилл Мокевнин — сооснователь школы программирования «Хекслет». В 2019 году по результатам голосования его наградили Премией HighLoad++ — за весомый вклад в IT-образование. Мы узнали у Кирилла, что для него значит Премия и как стать узнаваемым человеком в индустрии: https://habr.com/ru/companies/oleg-bunin/articles/775604/
Пётр Зайцев — основатель компании Percona по разработке ПО для работы с базами данных, предприниматель в области open source, инвестор, ментор и adviser. Кроме Percona, участвует в проектах Altinity, которые занимаются технологией ClickHouse; FerretDB — альтернативой MongoDB и ряде других. Мы расспросили Петра, как дойти до такого уровня экспертизы и что мешает современным IT-бизнесменам. 📍Подробности в статье: http…
Алексей Миловидов — разработчик и создатель технологии ClickHouse. Проект получил больше $2 млрд инвестиций. Эта распределенная аналитическая система управления базами данных с открытым исходным кодом используется компаниями со всего мира. Она столбцовая и позволяет онлайн обрабатывать аналитические запросы. Значения из разных столбцов хранятся отдельно, а данные одного столбца - вместе. За этот вклад в Open Source…
Олег Бартунов — научный сотрудник Московского государственного университета, генеральный директор компании Postgres Professional, Major contributor Postgres SQL и один из его создателей. А ещё он — лауреат первой Премии HighLoad++, которая существует с 2018 года. Мы расспросили Олега о том, каково быть лидером мнений в индустрии и что нужно делать, чтобы этого добиться. ⠀ 📍Подробности в статье: https://habr.com/ru/c…
Showing the 12 most recent of 20 posts we hold for @TestDrivenChannel. 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.
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.
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.
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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“TestDrivenChannel” (@TestDrivenChannel), 71 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/TestDrivenChannel.
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.