Telegram RegisterThe public register of Telegram

Channel

В IT чудес не бывает

@IT_without_miracles

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

896subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001912082808
TypeChannel
Username@IT_without_miracles
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/IT_without_miracles

Growth

8967 Aug 2026, 10:17 — 896 subscribers8 Aug 2026, 06:32 — 896 subscribers7 Aug 2026, 10:178 Aug 2026, 06:32
2 measurements taken within a single day. 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 895–897 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:32896no change
7 Aug 2026, 10:17896first reading

Engagement

20 posts held, back to 12 March 2026the 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 · 30 days
41.1%
avg views ÷ 896 subscribers
Avg views / post
368
3 posts measured
Reaction rate
3.26%
reactions ÷ views · ER floor
Posts in window
4
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 7 August 2026
Posts held20 (12 March 20267 August 2026)
Views total1,105
Reactions total36
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 10:17 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

218 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 56.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
12356.4%
👍2712.4%
🔥2411.0%
😱188.26%
😁135.96%
😢52.29%
💯41.83%
20.917%
💩20.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 19 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 218reactions 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 12 March 2026 to 7 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.

Recent posts

7 Aug 2026, 07:38 UTC197 views4 reactionsread 7 August 2026
Photo

2 интересных примера взаимодействия CPO и CTO. Как много из людей C-level готовы к открытому обсуждению проблем, вместо истории "они там ничего не шарят, щас мы тут сами все сделаем..."? Я встречал оба кейса в реальной жизни, но "правильный" кейс был очень редким. Но после разговора с "открытыми забралами" часто возникает вопрос и "что дальше?" Что на самом деле происходит между этими 2мя состояниями на картинке?

4

Signed Максим Шульга

6 Aug 2026, 07:18 UTCviews —

В IT чудес не бывает pinned «Не думал, что придется так скоро повторять прошлогоднюю историю (да и в принципе, что придется повторять "шаг на выход в никуда"), но решение принято. Я снова открыт к предложениям по возможному нанесению пользы в какой-нибудь интересной компании. Все как…»

6 Aug 2026, 06:28 UTC332 views29 reactionsread 7 August 2026

Не думал, что придется так скоро повторять прошлогоднюю историю (да и в принципе, что придется повторять "шаг на выход в никуда"), но решение принято. Я снова открыт к предложениям по возможному нанесению пользы в какой-нибудь интересной компании. Все как в прошлый раз, технический менеджмент в продуктовой разработке (не заказной), РФ. Любые форматы работы, но с фокусом на гибрид, так понятней и интересней (Питер).

😱1892

Signed Максим Шульга

29 Jul 2026, 14:36 UTC576 views3 reactionsread 7 August 2026

Скучали? Жизнь идет своей чередой, ключи все так же бьют по голове. Писать все так же не о чем, все мысли "съедаются" на подлете к "бумаге" 🙂 Зацепила статья, советы напомнили анекдот про филина-стратега. Но что-то в них есть. The Best Prioritization Is No Prioritization The better you are at moving fast the worse you can be at prioritization. Prioritizing well requires being very clever. Building fast is great be

1👍1💯1

Signed Максим Шульга

16 Jun 2026, 05:54 UTC800 views19 reactionsread 7 August 2026

Незаконченные консервативные #мысли_вслух Написание кода ишачком ускоряет процесс поставки в одном месте (которое, имхо, нечасто и было "узким" горлышком), но ярко подсвечивает проблемы других местах: продуктовом видении, планировании и взаимодействии. В итоге, есть риск того, что "расширив" пропускную способность в одном месте, мы просто положим систему переместив всю нагрузку туда, где производственная система мож

12👍5🔥2

Signed Максим Шульга

29 May 2026, 06:02 UTC922 views14 reactionsread 7 August 2026

IT-басни в пятничных #it_memes Мораль: Где начальников полно, Там продукт, увы, говно. Там, где ответственности ноль, Результат — сплошная боль. Ну что, может еще созвончик?

😁13🔥1

Signed Максим Шульга

28 May 2026, 05:37 UTC824 views5 reactionsread 7 August 2026

Читаешь чью-то очередную статью. Начинаешь писать сюда черновик заметки по ней. Бегаешь по связанным хештегам. Понимаешь, что уже писал похожее и сам, и статьи были. Кажется, что уже нет тем, которые тут не помусолил. И задумываешься, а для чего и кому нужна очередная история? Одна из причин моей пропажи тут. Но реально прикольно залипать на старых заметках: часто прямо вспоминается кейс на работе или что-то другое

3👍2

Signed Максим Шульга

27 May 2026, 05:39 UTC711 views2 reactionsread 7 August 2026
Photo

The un-hateable engineering managers The lie of Radical Candor and ruining an engineer's day I'm now willing to step into what might feel like Obnoxious Aggression to the other side, as long as I feel deep inside that I'm doing the right thing (which doesn’t mean always laying people off). I'm more ok with people being angry at me, not liking me, or even thinking I'm unfair. Hopefully it won't get to hate, but that

2

Signed Максим Шульга

26 May 2026, 05:53 UTC970 views25 reactionsread 7 August 2026

Почему все так закончилось? Да хз. С моей колокольни, которая и рядом не стояла там, где точно все видно было, видится как последовательная серия неправильно принятых решений (бизнес и технических) в разное время разными людьми: • неправильно определили целевую аудиторию продуктов • необычная кадровая политика на топ-уровне • "бессрочное" лицензирование с фокусом на поддержку, которую разработка конечно "завалила раб

11🔥10💯2👍1💩1

Signed Максим Шульга

26 May 2026, 05:53 UTC942 views16 reactionsread 7 August 2026

Вчера вся лента пестрила "новостями" о "грядущих" сокращениях в МойОфис, все это разбавлялось рассуждениями "экспертов" о причинах провала. Ну во-первых, про эти сокращения была публичная инфа парой месяцев раньше, странно что все так возбудились только сейчас, когда многие сокращенные (жаль, что пока не все конечно) уже на новую работу вышли. Кстати, приятное удивление - те, кто озаботился и подсуетился, достаточно

9🔥4👍2💩1

Signed Максим Шульга

23 Apr 2026, 09:14 UTC≈1,140 views50 reactionsread 7 August 2026

Всем привет Я думаю, что многие в курсе истории с МойОфис (НОТ) и того, что какую-то часть разработки там сокращают. Это тот момент, когда многих готов был бы взять без собесов и вот этого всего. Но во-первых все "не поместятся", а во-вторых каких-то специализаций у меня и вовсе нет. Обидно. Я понимаю про текущий рынок найма и то, что кандидатов на 1 место сейчас много (мягко говоря) и можно лениво ковырясь отбирать

45😢5

Signed Максим Шульга

8 Apr 2026, 06:46 UTC≈1,060 views13 reactionsread 7 August 2026
Video

#5for5 1. Про 1:1 Признак хорошей встречи: после нее сотрудник чувствует, что его работа была замечена, его проблемы были восприняты всерьёз, и его профессиональный рост действительно имеет значение. 2. О ваших исходниках замолвите слово… Why Your Engineering Team Is Slow (It's the Codebase, Not the People) Я бы не сказал, что это основная причина тормозов, но бывает и такое. Про 5 признаков проблем с исходниками и

13

Signed Максим Шульга

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

Citation-graph rank — 714,388 of 1,169,250entries 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

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

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

“В IT чудес не бывает” (@IT_without_miracles), 896 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/IT_without_miracles.

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.