Telegram RegisterThe public register of Telegram
Telegram profile photo for Макси́м Сурки́з – Создаю продукты

Channel

Макси́м Сурки́з – Создаю продукты

@surkiz_blog

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

697subscribers

+5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001432912776
TypeChannel
Username@surkiz_blog
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 September 2026
On Telegramt.me/surkiz_blog

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 20 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

6926986957 August 2026 — 692 subscribers7 August 2026 — 692 subscribers14 August 2026 — 698 subscribers22 August 2026 — 696 subscribers28 August 2026 — 698 subscribers5 September 2026 — 697 subscribers6977 August 20265 September 2026
6 measurements spanning 29 days, net +5. 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 691–699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 21:02697-1
28 Aug 2026, 03:25698+2
22 Aug 2026, 01:58696-2
14 Aug 2026, 14:14698+6
7 Aug 2026, 09:56692no change
7 Aug 2026, 09:48692first reading

Engagement

18 posts held, back to 16 October 2025 — the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

250 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14758.8%
😁3815.2%
❤3614.4%
👍2710.8%
👎20.8%

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

Measured over the 18 most recent posts we hold, published 16 October 2025 to 31 July 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
50
across the posts below
Posts paid on
15
of 18 we hold a reading for · 83%
Most on one post
12
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @surkiz_blog. 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 18 most recent posts we hold for this entry, published 16 October 2025 to 31 July 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

31 Jul 2026, 10:53 UTC182 views15 reactionsread 7 August 2026
Photo

ИИ есть, а доступа нет 🤖 Несколько лет назад, когда популярные ИИ сервисы один за другим начали блокировать доступ россиянам, я подумал: ну фигня какая-то. Мы уж точно найдём, как всё это обойти, оплатить и настроить. Оказалось, я сильно недооценил проблему. За последнее время я провёл несколько воркшопов в компаниях по работе с ИИ-агентами. И был неприятно удивлён: даже опытные разработчики и вполне технические л…

🔥12❤3

28 Jul 2026, 17:37 UTC268 views13 reactions1 Starread 7 August 2026

Телеком умер, да здравствует телеком! 📡 В далеком 2004 году я устроился админом в КрафтСвязь Новосибирск. Админил хостинг, почтовые серверы, D-link, Cisco, MERA, SIP, Asterisk и пр. Потом были Новотелеком, он же Электронный город, ИнфоСвязь... В общем, успел поработать во всех крупных провайдерах Новосибирска. Прошло 20 с лишним лет, и я снова пишу про телеком. Только теперь про AI.) В прошлую технологическую волну…

🔥13

13 May 2026, 13:30 UTC777 views5 reactions1 Starread 7 August 2026
Photo

Часто слышу переживания за джунов, а переживать нужно за синьоров… «…синьоры ещё куда-то нужны» ? 😕 @surkiz_blog

😁5

26 Apr 2026, 17:08 UTC833 views9 reactions2 Starsread 7 August 2026

Смотри, всю неделю был дождь. У меня грязная машина, мне нужно ее помыть. И всего в пяти минутах ходьбы есть замечательная мойка. А сейчас на улице прекрасная солнечная погода. Тепло, светло, зелено. Как думаешь, мне лучше пройтись пешком или доехать на машине? Давай взвесим плюсы и минусы Отправил этот вопрос почти во все модели, которые были под рукой. Справилась только одна. Угадайте, какая? @surkiz_blog

😁9

21 Apr 2026, 16:49 UTC891 views26 reactions3 Starsread 7 August 2026

Моя новая статья в Forbes вышла сегодня 🖌️ Следующий шаг ИИ – не интеллект, а действие в реальном мире. ИИ уже умеет планировать поездку, рекомендовать ресторан, составлять план работы. Но он до сих пор не может забронировать, оплатить или подтвердить. Разрыв между «вот что тебе нужно сделать» и «готово» – это и есть следующее поле конкуренции. В статье разбираю: — Что на самом деле нужно для ИИ-агентности в реаль…

🔥24❤2

17 Apr 2026, 22:09 UTC784 views31 reactions7 Starsread 7 August 2026

Сегодня закончили обучение по внедрению агентного ИИ в процессы разработки одной крупной компании. Руководство и менеджмент довольны, а сотрудников и технарей ждут перемены. Сейчас особенно важно быть готовым учиться новому и перестраивать свои рабочие процессы 🦾 Некоторые только-только освоили ChatGPT, как он устарел 😔 (я сам уже несколько месяцев как перестал им пользоваться). Год-два назад мне казалось, что техно…

❤14👍12🔥5

7 Mar 2026, 02:36 UTC738 views11 reactions1 Starread 7 August 2026
Photo

Спокойной ночи) 💤

😁11

26 Feb 2026, 00:18 UTC911 views17 reactions6 Starsread 7 August 2026

Жизненный цикл разработки ПО мертв? 😨 Борис Тейн написал статью я перевёл и выложил её тут. Главный тезис: ИИ-агенты не ускорили SDLC – они его убили. 😵 Вместо цепочки «требования → дизайн → код → тесты → ревью → деплой → мониторинг» осталось: «намерение → агент → наблюдение → повтор.» И я это наблюдаю на себе и когда строишь продукт с агентами, классический SDLC реально рассыпается, а Jira в этом процессе как фак…

🔥11👍4👎2

4 Dec 2025, 10:58 UTC≈1,050 views39 reactions1 Starread 7 August 2026
Photo

— "Что делается… Раньше шубы, мотоциклы доставали. Теперь детей доставать начали."(с) Кот Матроскин 🙀 А теперь награды за токены раздают) 🤖 Поздравляю нас! @surkiz_blog

🔥36😁3

16 Nov 2025, 21:26 UTC≈1,010 views9 reactions1 Starread 7 August 2026

2PR.io v2.0 Ислам, мой партнер по Copilot2trip перезапускает свой стартап 2PR.io на Product Hunt! В прошлый раз они уже выиграли и если у вас есть аккаунт на PH поддержите upvot’ом! https://www.producthunt.com/products/2pr-2?launch=2pr-v-2-0 Спасибо! 🙏

❤9

9 Nov 2025, 21:58 UTC971 viewsread 7 August 2026
Photo

Кто идёт на WebSummit? Давайте встретимся 🧁

30 Oct 2025, 10:44 UTC≈1,120 views10 reactions2 Starsread 7 August 2026

Чуть больше полутора лет спустя, новое интервью оказалось ещё лучше предыдущего. Вам нужно его посмотреть! 💯 P.S. Больше всего мне нравится наблюдать за работой их зеркальных нейронов) за тем, как братья научились синхронизировать два своих мозга в единое целое и это безусловно дает им преимущество! 🧠+🧠=🖐️ https://youtu.be/wp7izqZmiWM @surkiz_blog

🔥6👍3❤1

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Макси́м Сурки́з – Создаю продукты” (@surkiz_blog), 697 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/surkiz_blog.

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.