Channel
@dmitryonsoftware
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
114subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003765499862 |
|---|---|
| Type | Channel |
| Username | @dmitryonsoftware |
| Description | Пишу про разработку бэкэнда, Ruby, базы данных и техническое лидерство |
| Created | Between 1 February 2026 and 17 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dmitryonsoftware |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 05:47 | 114 | no change |
| 8 Aug 2026, 10:00 | 114 | first reading |
20 posts held, back to 17 March 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 18 July 2026 |
|---|---|
| Posts held | 20 (17 March 2026 – 18 July 2026) |
| Views total | 105 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 05:47 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.
Lifetime counters from Telegram’s own channel header, read 9 August 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.
109 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 54.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 59 | 54.1% | |
| 🔥 | 25 | 22.9% | |
| ❤ | 14 | 12.8% | |
| 😁 | 5 | 4.59% | |
| 👏 | 4 | 3.67% | |
| 🐳 | 1 | 0.917% | |
| 👌 | 1 | 0.917% |
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 17 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 109reactions 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 17 March 2026 to 18 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.
Мы с товарищем ради веселья собрали игру и выложили в стор. Получился roguelite city builder, нужно придумать как застраивать остров и распределять рабочих так, чтобы остров как можно дольше не затопило. 3 месяца, 0 строчек кода руками, 0 ассетов руками, тонна спецификаций написана и переписана. Работает. Ваш покорный слуга также родил аж 8 минут крафтового long form ambient для саундтрека. Технические посты и steam…
👍8🔥3
В этом году снова буду сидеть в ПК RubyRussia. Вы ходите? Когда посетили впервые? Я кажется в 2014
Всем привет! 👋 Мы открываем прием докладов на RubyRussia 2026! 2 октября мы снова встретимся в Москве, чтобы обсудить Ruby, обменяться опытом и провести день в кругу сообщества. А пока самое время стать частью программы конференции. 🔺До 1 сентября принимаем заявки на доклады. Если у вас есть интересная тема, необычный опыт, технический кейс или история, которой хочется поделиться, — отправляйте заявку. Мы поможем …
👏4
8 реакций но 3 звездочки (причем одна, как в известном меме, это самолайк)
Соорудил маленький гем sidekiq-requeue_missing_class (🐴🧔♂️) При rolling deploy старые и новые процессы какое-то время работают одновременно. Новый код может поставить в очередь job, класс которого старый воркер ещё не загрузил — получаем NameError: uninitialized constant SomeJob, хотя класс уже задеплоен. То же самое можно получить и при использовании schedule. Обычно это решают практикой протокола деплоя (двухфаз…
👍9❤2
Кто шарит в DDD? Продайте мне пожалуйста
😁2
Целый месяц ушел на то, чтобы перевести все заметки по LLM–слою в полноценный пост — почитайте, если предпочитаете версии на английском, и покажите англоговорящим коллегам 🙂
👍5🔥2
Saint P Rubyconf - 6 июня Конференция пройдет по адресу: Санкт-Петербург, Измайловский пр., 2 / наб. реки Фонтанки, 120 Анонсируем первые 2 доклада: 1️⃣ Сергей Малых (GroupPrice.ru) - Монолит 2.0: стратегия управления сложностью В жизни любого успешного проекта всегда наступает момент, когда требуется разделить кодовую базу, чтобы было легче им управлять. Обычно под этим подразумевают переход на микросервисную арх…
👍4❤1
Обстановка на DUMP в Екатеринбурге. 14 секций и 100 с чем-то докладов за день
👍7
Чуть освежил дизайн сайта, если вдруг не читали мои старые посты то велком https://dmitrytsepelev.dev
🔥8👍2
Слой LLM в Rails: пишем тесты Ранее мы написали запросы к LLM, теперь стоит их протестировать — но как? Модель недетерминирована, ответы не всегда соответствуют схеме, запросы стоят денег и занимают много времени. Из–за недетерминированности мы не можем применить обычный подход с webmock, но и выполнять реальные запросы тоже не хочется. Я в своих проектах пришел к следующей модели: юнит–тесты для тестирования логики…
🔥2
Уровень 2: промпт-тесты Промпт–тесты нужны для того, чтобы проверить, что в результате выполнения запроса нам приходит более–менее ожидаемый ответ. Почему более–менее? Потому что доказать, что ответ абсолютно всегда верный — невозможно, но мы хотя бы можем проверить некоторые случаи и сделать базовые проверки (например, что в boolean поле приходит boolean, а саммари текста — короче текста ) Для этого нужны промпт-т…
👍3🔥1
Showing the 12 most recent of 20 posts we hold for @dmitryonsoftware. 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.
Citation-graph rank — 639,686 of 1,160,990entries 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Дмитрий Цепелев | Дневник техлида” (@dmitryonsoftware), 114 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/dmitryonsoftware.
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.