Пятница. Значит, можно на время закрыть вкладки с документацией и открыть свежую пачку полезного от Слёрма. На этой неделе собрали три штуки: для собеседований, инцидентов и ИИ, который слишком многое знает. #️⃣ Технический гайд для DevOps собеседования Разобрали структуру интервью, 6 ключевых блоков вопросов и примеры сильных ответов. Пригодится перед собеседованием или чтобы проверить, насколько ты уже готов к De…

Channel
Слёрм
@slurmnews
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
8,088subscribers
-126 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001250858229 |
|---|---|
| Type | Channel |
| Username | @slurmnews |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/slurmnews |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:15 | 8,088 | +23 |
| 14 Sept 2026, 00:41 | 8,065 | -15 |
| 9 Sept 2026, 21:40 | 8,080 | -13 |
| 4 Sept 2026, 15:20 | 8,093 | -10 |
| 31 Aug 2026, 16:38 | 8,103 | -11 |
| 29 Aug 2026, 02:29 | 8,114 | -20 |
| 25 Aug 2026, 19:29 | 8,134 | -9 |
| 23 Aug 2026, 01:35 | 8,143 | -18 |
| 19 Aug 2026, 12:13 | 8,161 | -14 |
| 16 Aug 2026, 18:17 | 8,175 | -14 |
| 13 Aug 2026, 05:06 | 8,189 | -7 |
| 10 Aug 2026, 06:50 | 8,196 | -11 |
| 7 Aug 2026, 02:06 | 8,207 | -7 |
| 6 Aug 2026, 06:15 | 8,214 | no change |
| 6 Aug 2026, 06:07 | 8,214 | first reading |
Engagement
63 posts held, back to 27 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 21 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.85%
- avg views ÷ 8,088 subscribers
- Avg views / post
- 473
- 7 posts measured
- Reaction rate
- 0.713%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 63 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 28 August 2026 |
|---|---|
| Posts held | 63 (27 July 2026 – 28 August 2026) |
| Views total | 3,311 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:35 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
- 7s
- Average length
- 7s
Measured directly from 1 video 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
278 reactions across 50 posts, in 11 distinct kinds. The most used accounts for 29.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 81 | 29.1% | |
| ❤ | 69 | 24.8% | |
| 👍 | 48 | 17.3% | |
| 😁 | 37 | 13.3% | |
| custom 5418067966497422748 | 26 | 9.35% | |
| 💯 | 7 | 2.52% | |
| 👏 | 4 | 1.44% | |
| 🥰 | 3 | 1.08% | |
| 👎 | 1 | 0.36% | |
| 🤡 | 1 | 0.36% | |
| 🤣 | 1 | 0.36% |
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 54 of the 63 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 284 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 63 most recent posts we hold, published 27 July 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.
Recent posts
А вам слабо? 😏 Просто представьте… Сегодня вы впервые вышли дежурить в ночь. На часах 23:47. Половина стримингового графика страны держится на одном Kubernetes-кластере. Но что-то ломается. От вас ждут быстрого расследования и решения инцидента. Принимайте вызов и узнайте, насколько вы хороши. ➡️ Стартуйте бота и нажимайте «Начать игру»!
Kernel panic — что это такое и как с ним работать? Мы подготовили для вас инструкцию, в ней ответы на вопросы: 🔹почему ядро паникует на самом деле; 🔹как включить kdump и получить vmcore; 🔹что делать с crash и на что смотреть в первую очередь 👉 ЗАБРАТЬ ИНСТРУКЦИЮ Если после инструкции остались вопросы — это нормально, тема большая. Для тех, кто хочет копнуть глубже, у нас есть курс «Администрирование ОС Linux» Инс…
👍2🔥1custom 54180679664974227481
SRE может появиться в вашей работе раньше, чем в названии должности. Собрали несколько признаков, что с надёжностью сервиса уже пора работать системнее. Листайте карточки и считайте совпадения 👀 Если что-то узнали, можно не бросаться сразу в большой курс. У нас есть 7-дневный интенсив, где вы берёте знакомый сервис и собираете для него первый SRE-пакет: SLI/SLO, сигналы мониторинга, план на инцидент и postmortem. …
❤2🔥2
Когда выяснилось, что сертификаты есть, а нужные бизнесу навыки - нет☠️ 🎈Обучение IT-команды - это не просто «купили курс и отправили всех учиться». Если выбрать неподходящий формат, можно потратить деньги, время сотрудников и в итоге получить почти нулевой результат. ✅В статье разбирались, сколько на самом деле стоит ошибка в обучении IT-команд, из чего складывается стоимость обучения и как подобрать формат, котор…
😁4
🔥Бесплатно: проверьте себя на реальном DevOps-инциденте за 15 минут Знаете теорию, но не уверены, что справитесь с реальным инцидентом? Мы открыли бесплатный доступ к кейсу из Практикума «10 реальных инцидентов на стендах». Это полноценная задача целиком: рабочий стенд, задание «Nginx с приветствием», автопроверка результата и эталонное решение после сдачи. Что вы получаете бесплатно: 🔹живой стенд с уже сломанной …
👍1🔥1custom 54180679664974227481
Про SRE можно прочитать ещё десяток статей. Но к вашему сервису они сами себя не приложат 🛑 21 сентября стартует 7-дневный интенсив по SRE. Берёте знакомый сервис и за неделю разбираете его уже глазами SRE: что измерять, какой SLO поставить, на что алертить, что делать в первые минуты инцидента и что менять после него. В итоге всё собирается в ваш SRE-пакет по конкретному сервису, плюс становится понятно, куда дви…
👏2❤1👍1
А у вас в проде клауд-оркестрация больше похожа на первый или на второй вариант? 🔎
😁9
1 сентября разбираем реальные вакансии Junior DevOps🔥 Новый учебный год — хороший повод начать что-то новое. На этот раз — понятный план, как войти в DevOps и на какую зарплату рассчитывать Что будет: 1️⃣Живой разбор вакансий Разбираем требования и объясняем простым языком, что на самом деле стоит за каждым пунктом. 2️⃣Технический перевод Что на самом деле значит «знание K8s» для Junior. Сложное — простыми словами.…
🔥2👍1custom 54180679664974227481
🔮 У вас там сущность в виде докера Узнаёте симптомы? 👉 приложение работает локально, а на проде падает без объяснений 👉 deploy происходит через «зайти по SSH и помолиться» 👉 слово «контейнеризация» вызывает лёгкую панику 👉 на вопрос «а где ваш Dockerfile?» наступает неловкая пауза Если хотя бы один пункт откликнулся — сущность действительно поселилась. И изгонять её лучше не заговорами, а практикой. На курсе по Do…
😁2👍1🔥1
DKT Conference закончилась, а мы всё ещё немного там ❤️ 15 августа съездили на DKT Conference. От Слёрма на площадку отправились два наших представителя, и без дела они там точно не сидели. 🍕 Накормили участников пиццей 🎲 Раздавали стикеры и сувениры со Слёрмиком и маскотом DKT 🔎 Провели прямую трансляцию конференции на YouTube, чтобы к докладам могли присоединиться и те, кто не приехал офлайн ✨ А ещё от Слёрма выс…
🔥7🥰3
Прод упал, 23:47 🤯 Компания держит половину стримингового графика страны на одном Kubernetes-кластере. Сегодня ваша первая ночная смена. Ваша задача: изучить симптомы, провести расследование и решить, как устранить инцидент. Игра определит ваш уровень и точки роста. Готовы принять вызов? ➡️ Стартуйте бота и нажимайте «Начать игру»!
❤3👍2custom 54180679664974227481
Showing the 12 most recent of 63 posts we hold for @slurmnews. 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.
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 2 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@rebrain_devops · 28,890
Telegram ranks this channel #8 of 94 here — alongside 93 others — read 9 September 2026
@ITSTAND_ORG · 151,441
Telegram ranks this channel #17 of 98 here — alongside 97 others — read 9 September 2026
@geekbrains_ru · 24,719
Telegram ranks this channel #21 of 83 here — alongside 82 others — read 15 September 2026
@devopsforlove · 44,673
Telegram ranks this channel #25 of 95 here — alongside 94 others — read 9 September 2026
@yandexcloudnews · 21,888
Telegram ranks this channel #33 of 97 here — alongside 96 others — read 22 September 2026
@devops_jobs_feed · 21,793
Telegram ranks this channel #46 of 95 here — alongside 94 others — read 22 September 2026
@bashdays · 23,634
Telegram ranks this channel #75 of 94 here — alongside 93 others — read 18 September 2026
@Selectel · 63,289
Telegram ranks this channel #83 of 96 here — alongside 95 others — read 21 August 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Слёрм” (@slurmnews), 8,088 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/slurmnews.
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.