Telegram RegisterThe public register of Telegram
Telegram profile photo for Инструменты программиста

Channel

Инструменты программиста

@prog_tools

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

12,952subscribers

-57 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001533102168
TypeChannel
Username@prog_tools
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/prog_tools

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

12,95213,00912,980.56 August 2026 — 13,009 subscribers6 August 2026 — 13,009 subscribers6 August 2026 — 13,007 subscribers8 August 2026 — 13,003 subscribers9 August 2026 — 12,999 subscribers10 August 2026 — 12,998 subscribers11 August 2026 — 12,995 subscribers12 August 2026 — 12,992 subscribers14 August 2026 — 12,987 subscribers15 August 2026 — 12,978 subscribers17 August 2026 — 12,966 subscribers18 August 2026 — 12,963 subscribers20 August 2026 — 12,959 subscribers21 August 2026 — 12,955 subscribers22 August 2026 — 12,952 subscribers6 August 202622 August 2026
15 measurements spanning 17 days, net -57. 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 12,943–13,018 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 15:1512,952-3
21 Aug 2026, 05:5412,955-4
20 Aug 2026, 03:5312,959-4
18 Aug 2026, 08:2212,963-3
17 Aug 2026, 10:3612,966-12
15 Aug 2026, 19:1812,978-9
14 Aug 2026, 05:4712,987-5
12 Aug 2026, 19:5412,992-3
11 Aug 2026, 21:1612,995-3
10 Aug 2026, 19:4412,998-1
9 Aug 2026, 22:1312,999-4
8 Aug 2026, 02:3713,003-4
6 Aug 2026, 23:4713,007-2
6 Aug 2026, 02:3213,009no change
6 Aug 2026, 01:3513,009first reading

Engagement

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

ERR · 30 days
10.8%
avg views ÷ 12,952 subscribers
Avg views / post
1,400
44 posts measured
Reaction rate
0.262%
reactions ÷ views · ER floor
Posts in window
44
of 50 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 31 of 44 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 August 2026
Posts held50 (17 July 202622 August 2026)
Views total61,747
Reactions total95
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 13:49 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
1m 53s
Average length
57s

Measured directly from 2 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.

Reaction mix

102 reactions across 32 posts, in 14 distinct kinds. The most used accounts for 30.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3130.4%
👍2827.5%
😁1514.7%
🔥1413.7%
32.94%
21.96%
🗿21.96%
10.98%
❤‍🔥10.98%
🐳10.98%
👨‍💻10.98%
💯10.98%
🙈10.98%
🤣10.98%

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

Measured over the 50 most recent posts we hold, published 17 July 2026 to 22 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

22 Aug 2026, 10:35 UTC326 viewsread 22 August 2026
Photo

Bun — среда выполнения JavaScript и TypeScript, которая заодно работает пакетным менеджером, сборщиком и тест-раннером: один бинарник вместо связки node, npm, tsx и jest. 20 августа вышла версия 1.4. Главное в ней — совместимость: в набор, который гоняется на каждом коммите, добавили 1517 тестов из официального тестового набора Node.js; файлов этого набора теперь проходит 3743 против 1450 на версии 1.2. node:events

22 Aug 2026, 06:35 UTC501 viewsread 22 August 2026

DuckDB — аналитическая база, которая живёт внутри вашего процесса, как SQLite. Отличие в том, что SQLite заточена под много мелких операций со строками, а DuckDB под запросы, которые читают миллионы строк и считают агрегаты. Практический смысл: SQL прямо по файлам Parquet и CSV, без поднятия сервера и без загрузки данных куда-либо. Именно из-за этого сценария важен свежий выпуск 1.5.5 от 22 июля: файлы часто приходя

21 Aug 2026, 14:35 UTC674 views2 reactionsread 22 August 2026

В университетах учат алгоритмам и системам, но не учат пользоваться инструментами, на которых стоит вся работа. MIT сделал под это отдельный курс — The Missing Semester of Your CS Education: одиннадцать лекций примерно по часу, с конспектами, упражнениями и видео, бесплатно. Что разбирают: устройство оболочки и почему пробелы и кавычки ведут себя так странно; перенаправление потоков и конвейеры; сценарии на bash с п

👍1🙈1

21 Aug 2026, 10:35 UTC744 views1 reactionsread 22 August 2026

k6 гоняет нагрузочные тесты, которые пишутся обычным JavaScript и запускаются одной командой из терминала. Сценарий лежит в репозитории рядом с кодом, порог вида «99-й перцентиль меньше трёх секунд» описывается прямо в файле, а результат печатается в консоль или уезжает в дашборд. 🔘 HTTP, WebSockets, gRPC и браузерные сценарии в одном инструменте; 🔘 в версии 2.2.0 от 10 августа появился chromium.connectOverCDP(), то

👍1

21 Aug 2026, 06:35 UTC785 viewsread 22 August 2026

just — запускальщик команд проекта. Ту же роль обычно играет Makefile, но make всё-таки система сборки: он думает про файлы и зависимости, ругается на пробелы вместо табов и норовит не выполнить цель, если рядом лежит одноимённый файл. В justfile пишутся просто именованные команды с аргументами, и это всё, что нужно, когда цель — собрать в одном месте «прогнать тесты», «поднять окружение», «выложить». 3 августа вышл

20 Aug 2026, 16:35 UTC804 views3 reactionsread 22 August 2026

blitcp копирует файлы по карте диска: сначала строит карту, потом читает данные в том порядке, в каком они физически лежат. Задача та же, что у cp и rsync, разница проявляется на множестве мелких файлов и на медленных носителях, то есть на HDD, флешках и NAS. 🔘 склеивает мелкие файлы в один поток чтения; 🔘 пропускает дубликаты по хешу xxHash-128; 🔘 умеет reflink и жёсткие ссылки, понимает разрежённые файлы; 🔘 после

👍3

20 Aug 2026, 14:35 UTC804 views1 reactionsread 22 August 2026

Проблема с git не в командах, а в том, что непонятно, что они делают с графом коммитов. Learn Git Branching решает это буквально: вы вводите команду, и на экране двигаются кружочки и стрелки. Песочница живёт целиком в браузере, ничего ставить и регистрироваться не нужно. Уровни идут от простого к сложному: создание веток, движение HEAD, разница между merge и rebase, cherry-pick, отличие reset от revert, работа с уда

1

20 Aug 2026, 12:35 UTC852 views3 reactionsread 22 August 2026
Photo

DuckDB — база данных, которая живёт прямо внутри вашего процесса: ставится как библиотека, читает Parquet и CSV с диска и считает по ним аналитические запросы, без сервера и настройки. Примерно как SQLite, только заточенная не под строки, а под колонки и тяжёлые агрегаты. Авторы показали превью версии 2.0, релиз обещают осенью. Главная перемена в том, что база перестаёт быть только внутрипроцессной: расширение quack

🔥3

20 Aug 2026, 10:57 UTC813 viewsread 22 August 2026
Photo

⚡️ О!Хакатон возвращается — на кону миллион Приглашаем Go- и Python-разработчиков, аналитиков и продакт-менеджеров на тревел-тех хакатон от Островка. Вам предстоит решить одну из двух AI-задач в сфере тревел-теха и побороться за главный приз — 1 000 000 ₽. Присоединиться к хакатону можно из любой точки мира. Участвуйте командой до пяти человек и выбирайте один из двух треков: ✔️ «О!дин запрос». Цель для junior-спе

20 Aug 2026, 09:35 UTC822 views3 reactionsread 22 August 2026

Jujutsu, или jj, — система контроля версий, которая работает поверх обычного Git-репозитория: коллеги видят привычные ветки и коммиты, а у вас другая модель. Рабочая копия сама по себе коммит, staging area нет, любая операция отменяется через jj undo, конфликты хранятся в истории и не блокируют работу. 6 августа вышла версия 0.44.0, у проекта 31 тыс. звёзд на 17 августа. 🔘 стабилизирована работа с тегами: jj git fet

3

20 Aug 2026, 06:35 UTC876 views5 reactionsread 22 August 2026

OpenTelemetry Collector — прослойка между вашими сервисами и системами наблюдаемости. Сервисы шлют логи, метрики и трейсы в него, а он фильтрует, дописывает атрибуты и раскладывает по адресатам. Смысл в развязке: сменить систему хранения можно правкой конфига, не трогая код приложений. Fluent Bit и Vector делают похожее, но collector — эталонная реализация стандарта, и агенты под него пишут все. 4 августа вышла верс

2👍2🔥1

19 Aug 2026, 16:35 UTC913 views2 reactionsread 22 August 2026
Video

Плагин mobile-use даёт агенту в терминале управлять Android-телефоном: экран телефона рисуется прямо в боковой панели OpenCode, а агент нажимает, печатает, свайпает и открывает приложения через adb, каждый раз сверяясь со свежим скриншотом или дампом интерфейса. Автор показал это на видео. Внутри 12 инструментов — phone_tap, phone_swipe, phone_type, phone_dump_ui, phone_logcat, phone_shell и другие, — плюс готовые с

👍2

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

Citation-graph rank

Citation-graph rank — 209,209 of 1,584,142entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 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.

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.

Типичный программист
@tproger · 78,711
Telegram ranks this channel #11 of 95 here — alongside 94 others — read 19 August 2026
IT Юмор
@ithumor · 60,678
Telegram ranks this channel #42 of 94 here — alongside 93 others — read 22 August 2026
Библиотека программиста
@proglibrary · 78,409
Telegram ranks this channel #49 of 82 here — alongside 81 others — read 19 August 2026

This channel appears in 3 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“Инструменты программиста” (@prog_tools), 12,952 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/prog_tools.

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.