Полезная аналогия Даже если у тебя крутой навороченный харнесс, слабая модель не даст разогнать агента на максимум
👍18❤5custom 54562103083328009043

Channel
@artemshumeiko
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
19,767subscribers
-186 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001629983211 |
|---|---|
| Type | Channel |
| Username | @artemshumeiko |
| 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 | 17 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/artemshumeiko |
Education — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 20:00 | 19,767 | -4 |
| 14 Nov 2026, 13:20 | 19,771 | +2 |
| 11 Nov 2026, 12:21 | 19,769 | -10 |
| 9 Nov 2026, 16:34 | 19,779 | -8 |
| 8 Nov 2026, 10:41 | 19,787 | +2 |
| 7 Nov 2026, 03:00 | 19,785 | -8 |
| 6 Nov 2026, 03:36 | 19,793 | -2 |
| 5 Nov 2026, 04:11 | 19,795 | -8 |
| 4 Nov 2026, 01:21 | 19,803 | -12 |
| 3 Nov 2026, 03:46 | 19,815 | -6 |
| 1 Nov 2026, 02:29 | 19,821 | +1 |
| 31 Oct 2026, 02:40 | 19,820 | -13 |
| 30 Oct 2026, 04:30 | 19,833 | -34 |
| 29 Oct 2026, 04:31 | 19,867 | -14 |
| 27 Oct 2026, 00:34 | 19,881 | -5 |
| 26 Oct 2026, 03:57 | 19,886 | +5 |
| 25 Oct 2026, 00:29 | 19,881 | +5 |
| 24 Oct 2026, 03:48 | 19,876 | -4 |
| 23 Oct 2026, 00:49 | 19,880 | -9 |
| 22 Oct 2026, 02:51 | 19,889 | first reading |
59 posts held, back to 13 June 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 87 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 59 (13 June 2026 – 16 November 2026) |
| Views total | 130,780 |
| Reactions total | 742 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 17:05 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.
Measured directly from 6 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.
3,634 reactions across 59 posts, in 7 distinct kinds. The most used accounts for 37.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5456210308332800904 | 1,354 | 37.3% | |
| 👍 | 745 | 20.5% | |
| 🔥 | 735 | 20.2% | |
| ❤ | 711 | 19.6% | |
| 👏 | 37 | 1.02% | |
| custom 5415705042994870029 | 34 | 0.936% | |
| 🎉 | 18 | 0.495% |
Custom emoji. 2 of the rows above are 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 counts beside them are 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 59 of the 59 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 3,634 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 59 most recent posts we hold, published 13 June 2026 to 16 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @artemshumeiko. 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 59 most recent posts we hold for this entry, published 13 June 2026 to 16 November 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.
Telegram’s own ‘edited’ marker: 7 of 22 posts held from the last 30 days (31.8%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Полезная аналогия Даже если у тебя крутой навороченный харнесс, слабая модель не даст разогнать агента на максимум
👍18❤5custom 54562103083328009043
Поучительная история на ночь: как мы потеряли всю инфраструктуру, доступ к серверам и данным за одну ночь и как выбирались из этого говна Речь про мой стартап: https://solvit.space. Если сайт открывается, значит из говна мы выбрались) Приятного просмотра
❤50👍23custom 545621030833280090410
⚡️ Последний день набора на курс по микросервисам Сегодня до 23:59 МСК ты можешь успеть присоединиться к курсу "Микросервисная архитектура в продакшен разработке", а завтра, 10 ноября, мы начинаем обучение. Вести его будет Станислав Клоков, который проводил открытый урок. В Яндексе он занимался разработкой ядра платформы микросервисов, сейчас руководит командой в высоконагруженном финтех-проекте, а также преподаёт …
❤7
Зачем каждому микросервису своя база данных На первый взгляд может показаться, что и с одной базой все ок, зачем же тогда каждому сервису своя база?) Давайте разбираться Если все сервисы пилит один человек или маленькая команда, которая хорошо в них шарит, можно жить с общей базой. Договориться, кто с какими таблицами работает, аккуратно ходить за данными. Главное — не ломать чужие данные и учитывать зависимости от…
👍23❤7🔥4
Как проходит обучение на курсе по микросервисам в продакшен разработке Когда проектируешь микросервисы, каждое решение влияет на другие части системы и выбранные границы определяют взаимодействие сервисов, способ хранения данных влияет на бизнес-операции, а обработка отказов сказывается на поведении всего приложения. Поэтому на курсе каждую неделю будет отдельное практическое занятие, где ты внедришь материал лекци…
❤7custom 54562103083328009044👍3
Что часто не понимают о событийной архитектуре Можно добавить Кафку или RabbitMQ, перевести взаимодействие сервисов с http на сообщения — и так и не построить событийную архитектуру. Почему? Как вообще выглядит событийная архитектура? Давайте разбираться) Представим музыкальный сервис: музыкант добавил новый трек, а сервис каталога сохранил его в базе. Дальше сервис может отправить одно из двух сообщений: — Событи…
❤16👍7custom 54562103083328009041
Нужен ли твоим микросервисам брокер? При проектировании микросервисов приходится выбирать, достаточно ли в них обычного HTTP или нужен брокер сообщений. Чтобы принять решение, нужно разобраться, должен ли сервис получить результат сразу, можно ли отложить обработку и что произойдёт, если соседний сервис временно недоступен. Например, при оформлении заказа нужно проверить остатки, провести оплату и отправить уведомл…
❤8🔥6custom 54562103083328009042👏1
О моем печальном опыте работы с микросервисами Те, кто давно следит за каналом, знают, что я смотрю на код с двух сторон: со стороны разработчика и со стороны бизнеса. И во мне конфликтуют две идеи: об идеальном отлаженном протестированном коде и об идеальном бизнесе с огромной прибылью и "пофиг как" работающим продуктом. Чаще, конечно, побеждает разработчик-перфекционист 😂, но я тренирую себя трезво оценивать ситуа…
custom 545621030833280090431👍13❤2🔥1
Событийная архитектура — Простым языком 👉 Смотреть видео: YouTube / VK / Rutube Когда артист загружает альбом в музыкальный сервис, файлы нужно сжать, содержимое проверить, а тексты песен добавить в поиск. Если сервис загрузки будет ждать завершения всех этих операций, прежде чем вернуть ответ пользователю, придётся довольно долго смотреть на крутящийся индикатор, хотя сами файлы уже загружены В новом видео разобр…
🔥8custom 54562103083328009044❤2
⚡️ Открытый урок "Проектируем архитектуру маркетплейса: микросервисы на практике" Представь, что тебе поручили спроектировать маркетплейс наподобие Ozon. В нём будут каталог, заказы, оплата и остатки товаров, и тебе нужно решить, где провести границы сервисов и каким образом связать их между собой, а затем обосновать своё решение. 9 ноября в 19:00 МСК будем разбирать эту задачу на открытом уроке по микросервисам В…
❤10🔥3custom 54562103083328009043👏2
Какой проект ты будешь разрабатывать на курсе На протяжении шести недель ты будешь развивать интернет-магазин на Python с микросервисной архитектурой. В нём покупатель оформляет заказ, сервис оплаты обрабатывает платёж, склад резервирует товар, а пользователь получает уведомление и видит историю своих заказов. Вместе со Станиславом ты постепенно разделишь приложение на сервисы, наладишь взаимодействие между ними и …
❤10custom 54562103083328009043
Какие рабочие задачи ты сможешь решать после курса по микросервисам 10 ноября стартует курс "Микросервисная архитектура в продакшен разработке", который проведёт Станислав Клоков, экс-техлид Яндекса и тимлид высоконагруженного финтех-проекта. С паттернами можно познакомиться за вечер, но это не гарантирует успеха в работе, поскольку нужно также знать, куда вынести данные и что делать, если соседний сервис отвалитс…
❤6custom 54562103083328009043👍2🔥1
Showing the 12 most recent of 59 posts we hold for @artemshumeiko. 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.
@artemshumeiko edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 2 posts on @artemshumeiko as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 14 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Артём Шумейко” (@artemshumeiko), 19,767 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/artemshumeiko.
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.