Telegram RegisterThe public register of Telegram

Channel

Папочка Разработки

@dotnetdad

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

3,062subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002014256067
TypeChannel
Username@dotnetdad
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dotnetdad

Growth

3,0623,0643,0637 August 2026 — 3,064 subscribers7 August 2026 — 3,064 subscribers7 August 2026 — 3,063 subscribers10 August 2026 — 3,064 subscribers14 August 2026 — 3,062 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net -2. 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 3,062–3,064 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:353,062-2
10 Aug 2026, 23:413,064+1
7 Aug 2026, 17:103,063-1
7 Aug 2026, 13:313,064no change
7 Aug 2026, 13:113,064first reading

Engagement

20 posts held, back to 18 June 2026the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
61.1%
avg views ÷ 3,062 subscribers
Avg views / post
1,870
3 posts measured
Reaction rate
2.39%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 3 August 2026
Posts held20 (18 June 20263 August 2026)
Views total5,610
Reactions total134
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 13:31 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.

Reaction mix

1,031 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 43.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 526496168958913733644443.1%
👍34633.6%
11511.2%
custom 526485377853582433910810.5%
😁161.55%
🤔20.194%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 20 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 1,031reactions 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 18 June 2026 to 3 August 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
65
across the posts below
Posts paid on
3
of 20 we hold a reading for · 15%
Most on one post
42
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dotnetdad. 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 20 most recent posts we hold for this entry, published 18 June 2026 to 3 August 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

3 Aug 2026, 11:03 UTC≈1,140 views38 reactionsread 7 August 2026

Разработчик, который не перестроится под нейронки, никуда не денется. Он станет таксистом на волге у вокзала. Ты точно встречал такого мужика. Возраст, старая машина, работает без агрегаторов, стоит на своём месте лет пятнадцать. Называешь адрес — он молча кивает, потому что и так знает где твой дом. А если с ним разговориться, услышишь, как он презирает всех этих новых таксистов, которые без своего смартфона в цент

👍26custom 526496168958913733684

Signed Aleksandr Alekseev

22 Jul 2026, 11:35 UTC≈2,050 views14 reactionsread 7 August 2026

Видео для тех, кто всё хотел потыкать гошку, но руки не доходили 🌟. Сначала разбираемся что это вообще всё такое и как его по папкам разложить, а затем пишем код. Для практической части пригласил синьор голанг разработчика, который все эти приколы на работе каждый день видит. Сохраняем, смотрим, ставим лайки 🫡 https://www.youtube.com/watch?v=rMl2lTe5HiA

custom 52649616895891373369👍41

Signed Aleksandr Alekseev

17 Jul 2026, 12:01 UTC≈2,420 views82 reactionsread 7 August 2026

Если без тебя на проекте всё встанет — это не достижение. Это самая большая ловушка, в которую только можно попасть. Я раньше реально гордился тем, что я тот самый человек, без которого никуда. Знаю, как устроена самая страшная часть системы, помню, почему вот тут костыль, держу в голове весь контекст. Меня дёргали в отпуске, мне писали в выходные, и я в глубине души это любил — чувствуешь себя рокстаром и даже позв

👍50custom 5264853778535824339244custom 52649616895891373364

Signed Aleksandr Alekseev

14 Jul 2026, 07:47 UTC≈2,470 views76 reactionsread 7 August 2026

Код-ревью нужно не для того, чтобы ловить баги. И если у тебя на проекте оно про это — у вас всё плохо. Я лет шесть ревьюил чужой код, и за это время поймал глазами ну меньше десятка серьёзных багов. Реально критичных, которые ушли бы в прод — единицы. Зато комментов наоставлял тысячи. И в какой-то момент задумался: а что я вообще делаю? Баги ловят тесты, линтеры, статический анализ и прод в три часа ночи. Глазами

custom 526496168958913733648👍253

Signed Aleksandr Alekseev

10 Jul 2026, 16:19 UTC≈2,350 views100 reactionsread 7 August 2026

Я понял. Это вы не хотите пройти тренажер на джуна и оказаться внизу таблицы. Получается: идёшь на реальный собес, заваливаешь, потом идёшь тренироваться в боте, чтобы это не повторилось, а в нем тоже вниз какого-то рейтинга засунули и джуном заклеймили. Согласен — хуйня. Я бы тоже лишний раз не проходил 🌟. Так, последний шанс. Делаем отдельный соревновательный режим для самых смелых с публичным топом? Я жестко хо

custom 526485377853582433956custom 526496168958913733641😁21

Signed Aleksandr Alekseev

10 Jul 2026, 15:42 UTC≈2,060 views44 reactionsread 7 August 2026

Мощно тратите токены, но пока просто растет количество джунов 🌟. Донт ворри, тренажер действительно сложный) Будет интересно, если сделаю публичную таблицу лидеров? Там будут отображаться только верифицированные результаты, которые я лично сам глазами проверю. Конечно, там уже есть антифрод-система от откровенно нейронных ответов, но сейчас это впервую очередь инструмент для самообучения. Газ, делаем?

👍28custom 526485377853582433911😁5

Signed Aleksandr Alekseev

10 Jul 2026, 14:25 UTC≈2,050 views21 reactionsread 7 August 2026
Photo

Еще никто не прошел тренажер на синьорский грейд 🫡 Семь мидлов, почти двадцать джунов и ноль синьоров 🌟 У меня есть новая книжка по микросервисам, готов подарить первому, кто отправит в комменты картинку синьорского грейда в тренажере. ГАААААЗ! @booster_tbot Скопировать из нейронки не пройдет — попрошу показать ответы 🌟

custom 526496168958913733610custom 526485377853582433974

Signed Aleksandr Alekseev

9 Jul 2026, 15:25 UTC≈1,930 views40 reactions42 Starsread 7 August 2026

Последние два дня фуллтайм дотюнивал @booster_tbot, чтобы он перестал считать меня джуном. С задачей оптимизации токенов я не справился, но и хуй с ним — один раз живём. Мало того, что валидация так и осталась затратная, так я ещё и лучший транскрибатор подключил, который тоже токены тратит. Записываешь ему голосовое — он это всё в текст переводит и как ответ на собесе засчитывает 🌟 Можно посмотреть весь список во

21👍13custom 52649616895891373366

Signed Aleksandr Alekseev

8 Jul 2026, 08:55 UTC≈2,190 views33 reactionsread 7 August 2026

Решил сюда дублировать наш дайджест для учеников, который начали публиковать ежемесячно. Это второй. Если будет ноль устройств — напишу, что ноль. Если кто-то устроится на полторы деньги в год — так и будет в дайджесте. За все цифры и факты отвечаю и готов подтвердить 🫡. Дайджест надо читать полностью. Там и цифры по офферам и ситуация на рынке по вакансиям, которую мы собираем ежедневно. Названия компаний для пуб

12custom 526496168958913733610👍8custom 52648537785358243392😁1

Signed Aleksandr Alekseev

7 Jul 2026, 11:58 UTC≈1,530 views44 reactionsread 7 August 2026

Уже всё сделал, но это ахтунг конечно. Я бы такого бота самостоятельно писал минимум неделю, а в какой-то момент закопался в технической реализации, пошёл читать статьи и целый день потратил на штуку, которая ни на что не влияет 🥰. Список вопросов с вероятностями есть, мок-собесы есть, тесты написаны, логи собираются, а документация как в майкрософт. Всё это, конечно, кайфово, но у нас абьюзивные отношения и этот

custom 526496168958913733625👍118

Signed Aleksandr Alekseev

6 Jul 2026, 06:55 UTC≈1,820 views29 reactionsread 7 August 2026
Video message

Video message, posted without a caption

👍19😁64

Signed Aleksandr Alekseev

6 Jul 2026, 06:55 UTC≈1,830 views47 reactionsread 7 August 2026

Я не пропадал, просто десятикилограммовых щук ловил 🌟 Сейчас сажусь делать бота в телеге, который будет работать на результатах исследования трёхсот собесов, который собрал тут какое-то неимоверное количество реакций. Есть ещё мысли сделать там же тренажёр, где можно будет пройти имитацию собеса, выбрать уклон на какой-нибудь SQL или архитектуру и погонять себя перед интервью. Надеюсь, ближе к концу недели будем в

👍30custom 5264961689589137336107

Signed Aleksandr Alekseev

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

Citation-graph rank

Citation-graph rank — 102,095 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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

“Папочка Разработки” (@dotnetdad), 3,062 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dotnetdad.

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.