ЭТО БАГ ИЛИ ТАК ЗАДУМАНО? ❓ Как разграничить ответственность между UX/UI-дизайнером и Frontend-разработчиком? Дизайн согласован, вёрстка готова, дизайнер открывает страницу и разочарованно говорит, что всё не так, как в его макете. А Frontend-разработчик уверен, что сделал ровно то, что предложил дизайнер. Такие ситуации случаются постоянно. Но не потому, что кто‑то невнимательный. Обычно это системная история, ко…

Channel
Айтилогия | itlogia.ru
@itlogia
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,404subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001655518646 |
|---|---|
| Type | Channel |
| Username | @itlogia |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/itlogia |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 03:44 | 4,404 | +3 |
| 23 Aug 2026, 22:04 | 4,401 | +1 |
| 20 Aug 2026, 08:52 | 4,400 | +2 |
| 17 Aug 2026, 09:53 | 4,398 | +6 |
| 13 Aug 2026, 07:34 | 4,392 | -3 |
| 10 Aug 2026, 11:33 | 4,395 | +8 |
| 7 Aug 2026, 20:24 | 4,387 | -1 |
| 7 Aug 2026, 19:48 | 4,388 | no change |
| 7 Aug 2026, 19:34 | 4,388 | first reading |
Engagement
7 posts held, back to 30 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 4 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.96%
- avg views ÷ 4,404 subscribers
- Avg views / post
- 219
- 7 posts measured
- Reaction rate
- 1.32%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 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. It is computed over the 5 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 7 (30 July 2026 – 7 August 2026) |
| Views total | 1,530 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18: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
16 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 81.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 81.3% | |
| 🔥 | 2 | 12.5% | |
| 👍 | 1 | 6.25% |
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 5 of the 7 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 16reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 30 July 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
САМЫЕ ДОРОГИЕ БАГИ РАЗРАБОТЧИКОВ В ИСТОРИИ Все люди иногда ошибаются, но некоторые баги обходятся настолько дорого, что хочется закрыть ноутбук и навсегда уйти в лес. В этом посте мы собрали самые эпичные промахи разработчиков 🥹 Поверьте, на их фоне даже самый кривой из ваших коммитов выглядит невинно. Кстати, курс «Frontend-разработчик» способен свести к минимуму риск оказаться в неловкой ситуации из-за багов в к…
ЗАКОН ЯКОБА ИЛИ ПОЧЕМУ ПОЛЬЗОВАТЕЛИ ХОТЯТ, ЧТОБЫ ВАШ САЙТ БЫЛ КАК ВСЕ Закон Якоба или Джейкоба утверждает, что люди проводят большую часть времени на других сайтах и поэтому ожидают, что ваш ресурс будет работать так же, как привычные им платформы. Не потому что пользователям не хватает фантазии. Просто наш мозг стремится экономить энергию. И если мы видит на сайте знакомые паттерны, наши шансы дойти до цели выше. …
❤2
ЧТО ДОЛЖЕН ЗНАТЬ UX/UI-ДИЗАЙНЕР О HTML/CSS, ЧТОБЫ НЕ ССОРИТЬСЯ С РАЗРАБОТЧИКАМИ Чтобы проект удался, от UX/UI-дизайнера требуется не только подготовить красивый макет. Важно ещё и понимать, что произойдёт с ним на этапе вёрстки. Поэтому в своей статье Дарья Панкратова, выпускница курса «UX/UI-дизайнер», объяснила, какие базовые вещи из HTML и CSS стоит знать дизайнерам, чтобы потом не удивляться результату и не кон…
🔥2
А ЧТО БУДЕТ ПОСЛЕ КУРСА??? Один из самых частых вопросов, который мы слышим от будущих студентов и вопрос, который наверняка возникает и у вас 👇 «Я освою новую профессию, а дальше что? Как искать работу? Что делать, если мне будут постоянно отказывать?» У наших студентов уже есть ответ на эти вопросы — опытный карьерный консультант, который помогает пройти путь от подготовки к поиску работы до первых собеседований…
❤3
FRONTEND-РАЗРАБОТЧИКИ VS ВАЙБ-КОДЕРЫ: КЕМ БЫТЬ? ИИ сегодня обещает лёгкий путь в ИТ: «просто напиши промпт, и получи готовый сайт или приложение, как настоящий Frontend-разработчик». Но реальность куда жёстче: без базы в JavaScript и понимания архитектуры вы останетесь оператором нейронки, а не фронтендером. В свежей статье мы разбираем, чем отличается Frontend-разработчик от вайб‑кодера, и как использовать ИИ так…
❤1
АДАПТИВНЫЙ ДИЗАЙН ДЛЯ НАЧИНАЮЩИХ: КАК ПЕРЕСТАТЬ БОЯТЬСЯ МОБИЛЬНОЙ ВЕРСИИ И ПОЛЮБИТЬ ЕЁ 💖 Многие начинающие дизайнеры боятся адаптива. Но знаете, что страшнее? Сделать сайт только для десктопа и потерять больше половины пользователей. Согласитесь, сайт, который хорошо выглядит на любом экране, вызывает куда больше доверия, чем просто «красивая картинка» для широкого экрана. ❗️ Более 60% всего веб-трафика в мире пр…
❤7👍1
Showing the 7 most recent of 7 posts we hold for @itlogia. 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 — 432,660 of 1,622,561entries 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.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Айтилогия | itlogia.ru” (@itlogia), 4,404 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/itlogia.
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.