Telegram RegisterThe public register of Telegram
Telegram profile photo for Системный Аналитик

Channel

Системный Аналитик

@sys_sa

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

19,083subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001433682288
TypeChannel
Username@sys_sa
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held21
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/sys_sa

Growth

19,07719,09619,086.57 August 2026 — 19,081 subscribers7 August 2026 — 19,081 subscribers8 August 2026 — 19,077 subscribers9 August 2026 — 19,081 subscribers10 August 2026 — 19,082 subscribers11 August 2026 — 19,083 subscribers12 August 2026 — 19,089 subscribers13 August 2026 — 19,096 subscribers14 August 2026 — 19,088 subscribers16 August 2026 — 19,090 subscribers17 August 2026 — 19,091 subscribers18 August 2026 — 19,095 subscribers19 August 2026 — 19,094 subscribers20 August 2026 — 19,089 subscribers22 August 2026 — 19,082 subscribers23 August 2026 — 19,077 subscribers25 August 2026 — 19,084 subscribers27 August 2026 — 19,083 subscribers28 August 2026 — 19,084 subscribers29 August 2026 — 19,079 subscribers30 August 2026 — 19,083 subscribers19,0837 August 202630 August 2026
21 measurements spanning 23 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 19,074–19,099 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
30 Aug 2026, 12:4719,083+4
29 Aug 2026, 09:1419,079-5
28 Aug 2026, 11:5219,084+1
27 Aug 2026, 09:1419,083-1
25 Aug 2026, 04:3219,084+7
23 Aug 2026, 23:0619,077-5
22 Aug 2026, 07:3619,082-7
20 Aug 2026, 21:1619,089-5
19 Aug 2026, 22:5419,094-1
18 Aug 2026, 19:5619,095+4
17 Aug 2026, 20:0719,091+1
16 Aug 2026, 15:1519,090+2
14 Aug 2026, 20:4719,088-8
13 Aug 2026, 12:5919,096+7
12 Aug 2026, 15:2819,089+6
11 Aug 2026, 19:0419,083+1
10 Aug 2026, 20:0119,082+1
9 Aug 2026, 20:3119,081+4
8 Aug 2026, 18:4419,077-4
7 Aug 2026, 12:4619,081first reading

Engagement

22 posts held, back to 14 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 51 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
15.7%
avg views ÷ 19,083 subscribers
Avg views / post
2,990
2 posts measured
Reaction rate
0.468%
reactions ÷ views · ER floor
Posts in window
2
of 22 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 28 August 2026
Posts held22 (14 January 202628 August 2026)
Views total5,980
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 12:38 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

767 reactions across 21 posts, in 9 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
26935.1%
🔥19425.3%
👍16821.9%
😁9512.4%
111.43%
👏111.43%
🤣111.43%
💩40.522%
😢40.522%

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 21 of the 22 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 767reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 14 January 2026 to 28 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
4
across the posts below
Posts paid on
4
of 21 we hold a reading for · 19%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sys_sa. 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 22 most recent posts we hold for this entry, published 14 January 2026 to 28 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

28 Aug 2026, 07:03 UTC≈1,430 views13 reactionsread 30 August 2026

❓ ICAM (Incident Cause Analysis Method) ICAM (Incident Cause Analysis Method) — метод разбора инцидентов 💚 ищет системные причины, а не останавливается на ошибке конкретного человека 💚 по итогам разбора формулируют меры, чтобы инцидент не повторился 💚 Ключевой вопрос метода — не «кто виноват?», а «почему система это допустила?» 💚 Подходит для ИТ-инцидентов: сбоев систем, киберинцидентов, отказов бизнес-процессов

🔥74👍1👏1

19 Aug 2026, 09:09 UTC≈4,550 views15 reactionsread 30 August 2026

🖥 NewSQL NewSQL — класс реляционных СУБД, который совмещает привычный SQL и строгие ACID -транзакции классических баз (с горизонтальной масштабируемостью и производительностью, характерными для NoSQL) Попытка убрать главный компромисс хранения данных: ➖ классические реляционные БД надёжны и согласованы, но плохо масштабируются горизонтально ➖ NoSQL отлично масштабируется, но часто жертвует строгой согласованностью

10👍41

14 Jul 2026, 07:04 UTC≈7,740 views24 reactions1 Starread 30 August 2026

🔼 Server Driven UI (SDUI) Server Driven UI (SDUI) — архитектурный подход, при котором сервер определяет не только данные, но и структуру пользовательского интерфейса (какие компоненты, в каком порядке и с какими параметрами отрисовать на клиенте) 🍃В обычном приложении клиент «знает», как показать экран 🍃В SDUI клиент превращается в «движок рендеринга» — он просто отрисовывает то, что пришло с сервера в виде деклара

🔥158👍1

7 Jul 2026, 11:04 UTC≈7,860 views25 reactions1 Starread 30 August 2026
Photo

📊 Сравнение Баз данных и Хранилищ данных ▫️База данных – оперативное хранилище, где содержится "текущее состояние" бизнес-процессов: активные заказы, остатки на складе, профили пользователей и тд ▫️ OLTP (Online Transaction Processing) — обработка транзакций онлайн, способ эксплуатации этой базы 💙Хранилище данных (DWH)— информационная система, в которой хранятся данные из разных источников. Используется для анализ

👍137🔥4👏1

25 Jun 2026, 07:04 UTC≈10,100 views36 reactions1 Starread 30 August 2026

✏️ Принципы разработки KISS, Бритва Оккама, SSOT, DRY, YAGNI, SOLID Зачем нужны Инженерные принципы это не строгие правила, а ориентир Помогают: 🔸 уменьшать стоимость изменений 🔸 снижать количество ошибок 🔸 упрощать сопровождение 🔸 делать требования понятнее 🔸 избегать избыточных решений 💡 Для системного аналитика принципы служат фильтром при сборе требований, позволяют снизить затраты ещё до написания кода KISS

23👍8🔥5

18 Jun 2026, 07:04 UTC≈7,940 views13 reactionsread 30 August 2026
Forwarded from @lib_analystFile

Ретроспектива в Agile Проверенные методы и инновационные подходы ✍️ Автор: Марк Лоффлер 🗓 Год издания: 2020 🔤 Язык: русский 📚 Объём: 176 стр. Книга представляет систематизированное руководство по проведению Agile-ретроспектив. Рассматриваются 💙базовые принципы ретроспектив 💙этапы подготовки и проведения 💙а также роль фасилитатора. Описаны расширенные подходы, включая системные, распределённые и ориентированные на

🔥10👍21

16 Jun 2026, 07:04 UTC≈8,180 views18 reactionsread 30 August 2026

🖥 Cookie-файлы Cookie — небольшие данные, которые сайт сохраняет в браузере пользователя и использует при последующих запросах ⏩ Cookie — как номерок в гардеробе. Гардеробщик не запоминает лично, а выдает номерок, по которому находит вещи ⏩ Работают схоже: браузер хранит идентификатор, а сервер по нему понимает, кто выполняет запрос Протокол HTTP — stateless (не хранит состояние). Каждый запрос сам по себе не знае

🔥123👍3

29 May 2026, 13:55 UTC≈9,310 views24 reactions1 Starread 30 August 2026

🔽 Гонка событий (Race Condition) Гонка событий — ситуация, при которой результат работы системы зависит от порядка выполнения операций Если несколько процессов одновременно работают с одним состоянием, итог может быть непредсказуемым Может возникать в: 🟢микросервисах 🟢распределённых системах 🟢очередях сообщений 🟢асинхронных API 🟢frontend-приложениях 🟢потоковой обработке данных 🍃Сложность гонки событий: проблема пр

13🔥10👏1

16 May 2026, 07:10 UTC≈11,200 views25 reactionsread 30 August 2026

🛡 XSS-уязвимость XSS (Cross‑Site Scripting) — атака, при которой злоумышленник внедряет в веб‑страницу вредоносный код (обычно на JavaScript). Код выполняется в браузере другого пользователя (жертвы) ➡️ хакер находит место, куда можно «подложить» свой скрипт, когда жертва открывает страницу — скрипт крадёт её данные, подменяет содержимое или выполняет действия от её имени На этапе проектирования требований можно:

👍168👏1

20 Apr 2026, 07:06 UTC≈13,500 views20 reactionsread 30 August 2026

⌛ Impact mapping Impact mapping — техника планирования, которая помогает связать требования с бизнес-результатом Результат — визуальная карта, отвечает на вопросы по порядку: 1. Зачем это делаем? (Цель) 2. Кто может помочь или помешать? (Актор) 3. Как должно измениться их поведение? (Влияние) 4. Что можем создать, чтобы вызвать это изменение? (Результат) 💡 Не строятся функции. Меняется поведение акторов для до

👍11🔥54

3 Apr 2026, 15:46 UTC≈11,000 views23 reactionsread 30 August 2026

🌐 Web as Native WebView и Web as Native WebView — встроенный в мобильное приложение компонент, который отображает веб-страницы (HTML, CSS, JavaScript) внутри приложения Важно: 🔹 это не отдельное приложение (не Chrome/Safari) 🔹он управляется нативным кодом 🔹 пользователь не видит, что это веб Web as Native — подход, при котором веб-интерфейс используется как мобильное приложение Web — интерфейс и часть логики

184🔥1

19 Mar 2026, 15:31 UTC≈12,900 views44 reactionsread 30 August 2026

👍 LikeC4 LikeC4 — open-source инструмент моделирования архитектуры в нотации C4 Используется подход Architecture as Code — архитектура системы описывается на простом декларативном языке (DSL) Выполняет задачи: 💙 хранение архитектурной модели системы в репозитории 💙 авто-генерация диаграмм при изменении модели Это помогает поддерживать архитектурную документацию в актуальном состоянии LikeC4 позволяет описывать

27👍12🔥5

Showing the 12 most recent of 22 posts we hold for @sys_sa. 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 — 1,001,185 of 1,626,935entries 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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Системный и Бизнес-анализ
@ba_sa_analytics · 52,020
Telegram ranks this channel #18 of 90 here — alongside 89 others — read 24 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Системный Аналитик” (@sys_sa), 19,083 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/sys_sa.

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.