О Тайланде. Тут хорошо.
👍1

Channel
@programmers_vlog
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
83subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001516021657 |
|---|---|
| Type | Channel |
| Username | @programmers_vlog |
| Description | https://www.youtube.com/channel/UCJs_jjVQX9pMBba-b0DmBbw |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/programmers_vlog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 18:00 | 83 | no change |
| 7 Aug 2026, 16:23 | 83 | first reading |
20 posts held, back to 1 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 1 pageof 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. It is computed over the 6 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (1 June 2026 – 8 August 2026) |
| Views total | 361 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 18:00 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.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
9 reactions across 8 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9 | 100.0% |
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 8 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 9reactions 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 1 June 2026 to 8 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.
О Тайланде. Тут хорошо.
👍1
О самомнении. Бытует мнение что начальство тупое, ничего не понимает, то ли дело рядовые сотрудники. Не будем вдаваться в детали, бывает что руководство действительно не в курсе каких-то вещей, по тем или иным причинам. В некоторых случаях работники высказывают свое фи сложившемся процессам и ритуалам. И вот тут важный момент. Если работник высказывает фи и предлагает как исправить - это хороший работник. Если работ…
Оказывается работать не лицом в стену, а лицом в балкон 10/10. Переодически отводишь лицо от экрана, смотришь на деревья, очень приятно.
54 из 55 выявленных через AI уязвимостей в SQLite оказались фиктивными Исследователи из компании JFrog проанализировали опубликованные на днях 55 отчётов об уязвимостях в SQLite. На основании данных отчётов организация MITRE присвоила всем проблемам CVE-идентификаторы. Три проблемы получили статус критических, а самой опасной уязвимости (CVE-2026-51302) компания Red Hat присвоила в своих базах уровень 10 из 10, а S…
Сейчас готовлю свое мобильное приложение к запуску, какой же это юридический адок, то одно нужно, то другое (пишу чтобы выпустить пар)
👍1
Будущее наступило, это сообщение написано прямо с борта самолета в Ташкент
👍1
А можно еще полы мыть после работы? Пришли вот с вакансией 4 в одном тимлид, бек разраб, фронт разраб, продакт - обнять и плакать.
👍1
О задачах. Если раньше я ловил эстетическое удовольствие от проектирования архитектуры. То теперь, все больше получаю удовольствия от процесса постановки задач. Начну с эпиков. Под эпиками подразумеваю крупный блок функциональности, который включает в себя задачи для тестировщиков, бизнес аналитиков, разработчиков и еще кучу народу. Очень часто эпик ставится как «ну сделайте эту вот штуку, потому что она влияет на…
О смычке инженерии и бизнеса. Не первый раз бизнес кидается техническими требованиями и обсуждает что все будет сделано с помощью «технология name». Сейчас настала пора «агентов». Теперь за каждой простой функцией должен стоять агент (а мы, дураки, боялись что все на лямбды переедет). Оплата? Агент. Выбор самой дешевой цены? order by price desc limit 1? Нет! Агент! Важно помнить, бизнес не может диктовать техническ…
👍1
Posted without readable text
Хехе, нашел у себя черновик видео по собственному движку регулярных выражений. Вот думаю, надо его допиливать или нет. Кому сейчас какое дело зачем нужна компиляция регулярки и что она вообще дает, почему нельзя просто в лоб сравнивать по регулярке.
Хочу поговорить про инженерию. Переодически ставлю задачи на проектирование для разработчиков. В рамках этих задач нужно принести архитектуру будущего сервиса, и разделить на задачи. На уровне разработчика любовь к архитектуре часто обусловлена эстетикой. Классы красиво лежат, аккуратные абстракции. Сам любил такое. Но теперь, для меня как для менеджера, архитектура такая же утилитарная вещь как ножнички для ногте…
👍2
Showing the 12 most recent of 20 posts we hold for @programmers_vlog. 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.
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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Гамолин Максим (Boss of IT gym)” (@programmers_vlog), 83 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/programmers_vlog.
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.