Telegram RegisterThe public register of Telegram

Channel

Бестиарий программирования

@programming_tales

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

1,141subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001535631758
TypeChannel
Username@programming_tales
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/programming_tales

Growth

1,1401,1411,140.57 Aug 2026, 16:33 — 1,140 subscribers7 Aug 2026, 23:47 — 1,140 subscribers8 Aug 2026, 15:41 — 1,141 subscribers7 Aug 2026, 16:338 Aug 2026, 15:41
3 measurements taken within a single day, net +1. 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 1,140–1,141 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 15:411,141+1
7 Aug 2026, 23:471,140no change
7 Aug 2026, 16:331,140first reading

Engagement

17 posts held, back to 12 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
35.1%
avg views ÷ 1,141 subscribers
Avg views / post
400
15 posts measured
Reaction rate
1.51%
reactions ÷ views · ER floor
Posts in window
15
of 17 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 14 of 15 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 7 August 2026
Posts held17 (12 July 20267 August 2026)
Views total6,003
Reactions total83
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:47 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.

Reaction mix

98 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3232.7%
🔥2222.4%
😁1313.3%
🤣99.18%
66.12%
👏55.10%
😭55.10%
🤓44.08%
👨‍💻11.02%
😢11.02%

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

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

7 Aug 2026, 06:54 UTC161 views5 reactionsread 7 August 2026

Элегантность кода благодаря C++23 Продолжим разбирать приёмы рефакторинга и посмотрим, как std::ranges::views::enumerate помогает сделать код более элегантным. В заметке я рассматривал рефакторинг и оптимизацию кода за счёт объединения циклов. В итоге я остановился на следующем варианте кода: static TensorImpl make_contiguous_tensor(const std::vector<int64_t>& sizes) { auto q = sizes.size(); std::vector<int64_t

👍5

5 Aug 2026, 12:25 UTC235 views4 reactionsread 7 August 2026
Photo

О механизмах запуска PVS-Studio при работе с embedded-проектами на C и C++.

🔥4

4 Aug 2026, 18:48 UTC264 views2 reactionsread 7 August 2026
Forwarded from @kokuykinPhoto

OWASP выпустил новую версию Top 10 for LLM Applications 2026. 1. Prompt Injection 2. Sensitive Information Disclosure 3. Excessive Agency 4. Supply Chain 5. Data and Model Poisoning 6. Unbounded Consumption 7. Misinformation 8. Hidden Context Exposure 9. Vector and Embedding Weaknesses 10. Improper Output Handling Как и другие гайды проекта, этот список формировался силами сообщества. Участники предлагали новые кат

👍2

4 Aug 2026, 13:28 UTC289 views12 reactionsread 7 August 2026

Когда ИИ платят за строки кода :) static int ksys_read(int fd, char *buf, u32 len) { u32 i; char c; int pid = (int)ring3_current_pid; int slot; if (fd != 0 || !buf) { if (fd != 0 || !buf) { if (fd == 0) { return ERR_FAULT; } } } .... } Проверка эквивалентна if (!buf && fd == 0) return ERR_FAULT; и выглядит подозрительно. Но мне сейч

😁12

3 Aug 2026, 14:38 UTC365 views1 reactionsread 7 August 2026

Кто сразу видит ошибку в реализации паттерна double-checked locking в Java коде? :) public class KubernetesDevUIProcessor { static volatile List<Manifest> manifests; public List<Manifest> getManifests() throws BootstrapException { if (manifests == null) { synchronized (Holder.class) { if (manifests == null) { manifests = new ArrayList<>(); .... try (CuratedApplicati

👍1

27 Jul 2026, 11:50 UTC491 viewsread 7 August 2026
Forwarded from @pvsstudio_rusPhoto

В этот чудесный летний день мы предлагаем вам сделать коллаборацию! 🔥 А какие варианты взаимодействия есть и куда писать — можно узнать по ссылке 🔗 #PVS_Studio #статья

24 Jul 2026, 07:19 UTC542 views7 reactionsread 7 August 2026
Forwarded from @pvsstudio_rusPhoto

Статический анализатор — мощный, но не всегда простой инструмент. Поэтому мы подготовили для вас курс "Статический анализатор PVS-Studio на практике"! Что вас ждет: - Вы узнаете возможности анализатора, актуальные требования ГОСТ и как устроено лицензирование PVS-Studio. - Познакомитесь с локальной работой с PVS-Studio в плагине для IDE. - Поймёте, как встроить PVS-Studio в рабочий процесс разработки и минимизирова

🔥7

20 Jul 2026, 14:36 UTC567 views7 reactionsread 7 August 2026
Photo

Ошибка, которую никто никогда не совершал. Ведь так, да? Уже с первого курса университета — или даже раньше — вы могли догадаться, что писать arr[len(arr)] — плохая затея. И вряд ли так кто-то может ошибиться, правда? Мы тоже так думали, пока не проверили 1000 проектов. Прогрев Go анализатора :)

🤓4🔥3

20 Jul 2026, 13:57 UTC505 views3 reactionsread 7 August 2026
Photo

Хорошая новость для разработчиков на Unreal Engine: мы сделали PVS-Studio доступнее, и теперь анализ UE-проектов в PVS-Studio доступен в лицензии Team, а не только в Enterprise. Подробности. Если вы работаете с Unreal Engine и давно присматривались к PVS-Studio, то сейчас самое время попробовать анализатор на своём проекте. А если возникнут вопросы по интеграции или настройке, наша команда поддержки всегда поможет

👍3

18 Jul 2026, 15:03 UTC445 views6 reactionsread 7 August 2026
Photo

kstrncmp uint64_t kstrncmp(char *str1, char *str2, uint64_t len){ uint64_t index_str = 0; uint64_t different_char = 0; while (index_str < len) { if (str1[index_str] != str2[index_str]) { different_char++; } index_str++; } return different_char; }

😭5👨‍💻1

18 Jul 2026, 09:50 UTC417 views13 reactionsread 7 August 2026
Photo

Кажется я превратился в тролля. Но автор заслужил :) Мой комментарий к статье "Операционная Система на C без знаний C". Я так понимаю, речь идёт об этом проекте OS. Мдя. Ну что же, автору предстоит узнать ещё много о языке С. Например, что такое выход за границу буфера. void terminal_write_hex(uint64_t hex_num) { uint64_t index_buffer = 0; char buffer[sizeof(uint64_t)]; if (hex_num == 0x0) { ter

🤣9🔥3😢1

16 Jul 2026, 16:13 UTC471 views5 reactionsread 7 August 2026
Forwarded from @CBD_BCPhoto

Современная разработка начинается с правильных инструментов. Завершился курс «Инструментальные средства ЗОСРВ «Нейтрино». Слушатели познакомились с инструментами разработки, отладки, анализа и верификации ПО для Нейтрино. Особое внимание было уделено работе с комплектом разработчика, его интеграции со статического анализатора PVS-Studio, системой сборки, а также инструментами анализа системных событий. Это позволи

👍41

Showing the 12 most recent of 17 posts we hold for @programming_tales. 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 — 847,194 of 1,169,250entries 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.

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

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.

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

“Бестиарий программирования” (@programming_tales), 1,141 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/programming_tales.

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.