Telegram RegisterThe public register of Telegram
Telegram profile photo for Системный анализ | Дмитрий Помаскин

Channel

Системный анализ | Дмитрий Помаскин

@system_analysis_school

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry

1,391subscribers

+17 since we began measuring on 2 September 2026

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

Register entry

Telegram ID-1002693451824
TypeChannel
Username@system_analysis_school
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/system_analysis_school

Topic

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 why it has no browse page of its own yet.

Growth

1,3741,3911,382.52 September 2026 — 1,374 subscribers3 September 2026 — 1,383 subscribers9 September 2026 — 1,388 subscribers13 September 2026 — 1,389 subscribers17 September 2026 — 1,391 subscribers2 September 202617 September 2026
5 measurements spanning 15 days, net +17. 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 1,371–1,394 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 07:001,391+2
13 Sept 2026, 11:211,389+1
9 Sept 2026, 12:581,388+5
3 Sept 2026, 20:211,383+9
2 Sept 2026, 14:311,374first reading

Engagement

20 posts held, back to 30 June 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.9%
avg views ÷ 1,391 subscribers
Avg views / post
221
2 posts measured
Reaction rate
4.08%
reactions ÷ views · ER floor
Posts in window
2
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 2 September 2026
Posts held20 (30 June 20262 September 2026)
Views total441
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 14: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.

What this channel posts

Video runtime
22m 23s
Average length
3m 12s

Measured directly from 7 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.

Reaction mix

195 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 50.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9950.8%
👍6332.3%
custom 5845830268044185765178.72%
👏73.59%
🤔63.08%
😁21.03%
🤯10.513%

Custom emoji. One row above is a 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 count beside it is Telegram’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 18 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 195 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 30 June 2026 to 2 September 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
3
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @system_analysis_school. 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 30 June 2026 to 2 September 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

2 Sept 2026, 12:50 UTC114 views5 reactionsread 2 September 2026
Video

❗️L7-балансировщики❗️ Продолжаем разговор про балансировку нагрузки в наших системах 🫡 Сегодня простым языком рассказал ключевые аспекты L7-балансировщиков. В следующем посте будет видео с наглядными примерами применения обоих типов. 🔝 Паблик VK 😀 Системный анализ и архитектура | Дмитрий Помаскин

🔥3👍2

27 Aug 2026, 12:48 UTC327 views13 reactionsread 2 September 2026
Video

❗️Балансировщики нагрузки❗️ Следующий элемент, который мы разберем, это балансировщики нагрузки. В видео попытался максимально просто объяснить, в каких случаях вам понадобиться L4-балансировщик. А в следующем посте поговорим о L7 и разберем ключевые отличия механизмов друг от друга. 🔝 Паблик VK 😀 Системный анализ и архитектура | Дмитрий Помаскин

🔥12👍1

21 Aug 2026, 13:06 UTC461 views13 reactionsread 2 September 2026
Video

❓Когда CDN не нужен?❓ Часто на собеседованиях и консультациях при решении задач по system design замечаю, что люди добавляют CDN только из-за того, что знают о его существовании и считают обязательным компонентом любой highload-системы. В видео рассказал, в каких случаях CDN не просто будет бесполезен, а может навредить вашему проекту. P.S. Главная мысль вообще "Не усложнять там, где это не нужно". Подобные момент

🔥8👍5

13 Aug 2026, 14:45 UTC655 views23 reactionsread 2 September 2026
Video

❗️CDN на пальцах❗️ На консультациях за последние полгода часто замечаю, что, при проектировании систем, сложности у людей начинаются, когда касаемся инфраструктурных компонентов. Постарался очень коротко и понятно рассказать, что такое Content Delivery Network и для чего он нужен🫡 Да простят меня инфраструктурные магистры за такое упрощение☹ Обычно теоретические видео записываю в простом разговорном формате, но т

custom 584583026804418576517🔥6

7 Aug 2026, 13:59 UTC687 views4 reactionsread 2 September 2026

✅ Запись открыта ✅ 15.08 12:00 МСК System Design Для записи жмите сюда 👈 🔝 Паблик VK 😀 Системный анализ | Дмитрий Помаскин

🔥4

7 Aug 2026, 10:32 UTC650 views7 reactionsread 2 September 2026

❗️15.08 System Design❗️ System Design впереди с большим отрывом, думаю, что тянуть с голосованием смысла нет:) ✅ Запись будет открыта сегодня в 17:00 МСК ✅ Когда: 15.08 12:00 МСК Уровень: Middle. Требуемые навыки: Понимание принципов работы распределённых систем, брокеры сообщений, базовые отличия СУБД. Кол-во участников: до 4. Длительность: ~4 часа. Программа: ✅ Все этапы решения задач; ✅ Общие паттерн system des

👍4🔥3

6 Aug 2026, 12:30 UTC556 viewsread 2 September 2026
Poll

Тема занятия 15.08 12:00 МСК

  1. REST API23%
  2. Базы данных (с нуля)14%
  3. Базы данных (middle)34%
  4. Брокеры сообщений27%
  5. Функциональные требования32%
  6. Event-Driven Architecture34%
  7. Нотация С430%
  8. System Design52%
  9. Не смогу прийти / посмотреть результат30%

The shares total 276%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

6 Aug 2026, 12:30 UTC508 views4 reactionsread 2 September 2026

❗️Интенсивы августа❗️ Как вы могли заметить, я долго не выкладывал расписание занятий августа. Это было связано с некоторым непониманием своего графика 🙃 ❓Для тех, кто не понимает, о каких интенсивах речь, рассказал тут. В августе смогу провести только один интенсив 15.08 (суббота) в 12:00 по МСК, предлагаю сразу выбрать тему, опрос, как всегда, ниже 👇 Описание программ: 🔸REST API; 🔸Базы данных (с нуля); 🔸Базы да

👍2🔥2

5 Aug 2026, 13:00 UTC545 views6 reactionsread 2 September 2026
Photo

❗️Очередная задачка с собеса❗️ В этот раз разобрал задачку по System Design, которую дали ученику во время интервью на позицию Solution Architect ↗️ Она достаточно простая, поэтому запросто может прилететь и на позиции senior СА, так что обязательно посмотрите. Чем примечательна задача? Подобные задачи подразумевает не одно решение, а несколько последовательных итераций. Интервьюер постоянно добавляет новые услов

👍5🔥1

30 Jul 2026, 13:01 UTC702 views23 reactionsread 2 September 2026
Video

❓GET с телом?❓ Неожиданно появился новый HTTP-метод ⁉️ Без преувеличения можно сказать, что такое случилось впервые в этом тысячелетии. Да-да, сам в шоке, мне на консультации рассказали пару дней назад, решил вынести это дело в массы. Метод был назван QUERY, и представляет собой GET с телом, такие вот дела. Привет всем адептам отправки тела в GET 🤦‍♂ Остальные свойства аналогичны. Вот небольшое сравнение методо

🔥14👍6👏3

21 Jul 2026, 13:08 UTC768 views15 reactionsread 2 September 2026
Photo

🤖 Так ли важно уметь работать с ИИ? 🤖 В посте про навыки разных грейдов не смог уместить мысли про ИИ, поэтому, как и обещал, освещаю своё виденье отдельно. Пост также будет текстовым, так как является логическим продолжением предыдущего 🫡 В самом начале обозначу границы: речь пойдёт про использование инструментов в роли конечного пользователя, а не про внедрение ИИ для бизнеса. В вакансиях все чаще встречается тр

👍8🔥5🤔2

15 Jul 2026, 13:55 UTC783 views25 reactionsread 2 September 2026
Photo

🌟Да будет холивар 🌟 Предвижу, что за этот пост мне знатно прилетит, но я обещал его сделать, поэтому вот он 😎 Сегодня поговорим о том, какими хардами, по моему субъективному мнению, должны обладать специалисты на разных грейдах. Без классического видеоформата, потому что в тексте можно нагляднее сравнить. Дабы не дублировать строчки, писал только в сторону усложнения от грейда к грейду. Ну что ж поехали... 💫 Ст

🔥14👍6👏3😁2

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

6 Aug 2026, 12:30 UTCFinal Results44 voters

Тема занятия 15.08 12:00 МСК

  1. REST API23%
  2. Базы данных (с нуля)14%
  3. Базы данных (middle)34%
  4. Брокеры сообщений27%
  5. Функциональные требования32%
  6. Event-Driven Architecture34%
  7. Нотация С430%
  8. System Design52%
  9. Не смогу прийти / посмотреть результат30%

The shares total 276%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

3 Jul 2026, 13:04 UTCFinal Results16 voters

Тема занятия 12.07

  1. Базы данных (с нуля)19%
  2. Базы данных (middle)31%
  3. Брокеры сообщений25%
  4. Функциональные требования31%
  5. Event-Driven Architecture56%
  6. Нотация С431%
  7. System Design38%

The shares total 231%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 30 June 2026 to 2 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Системный анализ | Дмитрий Помаскин” (@system_analysis_school), 1,391 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/system_analysis_school.

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.