Telegram RegisterThe public register of Telegram
Telegram profile photo for Заметки программиста

Channel

Заметки программиста

@progersbooks

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Telegram's recommendations · Cite this entry

8,120subscribers

-182 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001474186642
TypeChannel
Username@progersbooks
Description№ 4931134716 Всё, что связано с айти и разработкой. По вопросам сотрудничества: @adv_and_pr
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/progersbooks

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@progersbooks/2606 · this entry20 Jul 2026, 20:03 UTC@itainik/149820 Jul 2026, 20:03 UTC1.00under a minute
@progersbooks/2608 · this entry23 Jul 2026, 19:40 UTC@itainik/150023 Jul 2026, 19:40 UTC1.00under a minute
@progersbooks/2627 · this entry21 Aug 2026, 20:53 UTC@itainik/152021 Aug 2026, 20:53 UTC1.00under a minute
@progersbooks/2629 · this entry25 Aug 2026, 20:50 UTC@itainik/152225 Aug 2026, 20:50 UTC1.00under a minute
@progersbooks/2669 · this entry17 Oct 2026, 20:17 UTC@itainik/156317 Oct 2026, 20:17 UTC1.00under a minute
@progersbooks/2672 · this entry20 Oct 2026, 20:57 UTC@itainik/156620 Oct 2026, 20:57 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@itainik53 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (42–11)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 11 of the 11 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 56 comparable posts for this entry, running 8 July 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @progersbooks — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

8,1208,3028,2117 August 2026 — 8,302 subscribers7 August 2026 — 8,300 subscribers10 August 2026 — 8,295 subscribers13 August 2026 — 8,287 subscribers16 August 2026 — 8,279 subscribers19 August 2026 — 8,274 subscribers22 August 2026 — 8,265 subscribers25 August 2026 — 8,263 subscribers28 August 2026 — 8,256 subscribers31 August 2026 — 8,250 subscribers3 September 2026 — 8,244 subscribers8 September 2026 — 8,239 subscribers12 September 2026 — 8,237 subscribers16 September 2026 — 8,235 subscribers2 October 2026 — 8,208 subscribers9 October 2026 — 8,192 subscribers14 October 2026 — 8,187 subscribers17 October 2026 — 8,182 subscribers20 October 2026 — 8,174 subscribers23 October 2026 — 8,165 subscribers26 October 2026 — 8,159 subscribers29 October 2026 — 8,150 subscribers1 November 2026 — 8,140 subscribers4 November 2026 — 8,133 subscribers7 November 2026 — 8,125 subscribers10 November 2026 — 8,120 subscribers7 August 202610 November 2026
26 measurements spanning 95 days, net -182. 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 8,093–8,329 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
10 Nov 2026, 07:478,120-5
7 Nov 2026, 03:468,125-8
4 Nov 2026, 13:088,133-7
1 Nov 2026, 02:558,140-10
29 Oct 2026, 11:318,150-9
26 Oct 2026, 00:168,159-6
23 Oct 2026, 01:198,165-9
20 Oct 2026, 04:018,174-8
17 Oct 2026, 11:368,182-5
14 Oct 2026, 01:458,187-5
9 Oct 2026, 12:358,192-16
2 Oct 2026, 16:398,208-27
16 Sept 2026, 11:588,235-2
12 Sept 2026, 10:418,237-2
8 Sept 2026, 11:168,239-5
3 Sept 2026, 14:168,244-6
31 Aug 2026, 06:278,250-6
28 Aug 2026, 11:168,256-7
25 Aug 2026, 18:348,263-2
22 Aug 2026, 16:338,265first reading

Engagement

56 posts held, back to 8 July 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 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.43%
avg views ÷ 8,120 subscribers
Avg views / post
522
23 posts measured
Reaction rate
0.217%
reactions ÷ views · ER floor
Posts in window
23
of 56 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 4 of 23 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 10 November 2026
Posts held56 (8 July 2026 – 10 November 2026)
Views total12,007
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 01:03 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

Photos
≈227
Videos
≈1
Links
≈1,600

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

12 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤12100.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 14 of the 56 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 56 most recent posts we hold, published 8 July 2026 to 10 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.

Advertising

Ad load
1.79%
1 of 56 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
691
over 1 measured post
Median views · rest
626
over 55 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFGqBSt1120 July 202620 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 56 most recent posts we hold, published 8 July 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 23 posts held from the last 30 days (0%) 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).

10 Nov 2026, 20:54 UTC91 viewsread 11 November 2026

🔥 Болтаем про IT Беседа с iOS-разработчиком, контент-мейкером, лидером сообщества осознанная меркантильность на тему баланс между сотрудником и компанией и личной жизни. Здесь вы узнаете, что не так с IT конференциями, что не так с 8-ми часовым рабочим днём и действительно ли IT для избранных? https://youtu.be/h6Nnt33v2Ns

9 Nov 2026, 20:54 UTC242 viewsread 11 November 2026

⚙️ За что все ненавидят JavaScript Несмотря на то, что JavaScript предоставляет программистам целую кучу возможностей, фреймворков и удобных инструментов, у этого языка всё равно есть целый ряд недостатков. В этом видео приведены как минимум 7 причин, которые поспособствовали тому, что многие считают JavaScript ужасным языком. Если вы новичок, то рекомендуем ознакомиться с ними заранее, чтобы в будущем они не стали…

8 Nov 2026, 20:24 UTC314 views1 reactionsread 11 November 2026

👨‍🎨 Как правильно настроить фотошоп Вернее, не «как правильно» настроить фотошоп, а как сделать это так, чтобы конкретно вам было удобно им пользоваться. Как ни крути, лишние инструменты и вкладки, открытые в неподходящем месте, могут сильно повлиять на вашу продуктивность. Это видео подойдёт как для новичков, которые только вчера открыли фотошоп, так и для опытных дизайнеров, которые просто хотят немного оптимизир…

❤1

6 Nov 2026, 19:48 UTC409 views0 reactionsread 11 November 2026

🐍 Что написано на Python В этом простом видео вы узнаете о 7 популярных программах и сайтах, которые написаны именно на этом языке. Отличный вариант для того, чтобы понять, на что он способен и какие у него есть перспективы. https://youtu.be/c4JzWn0yQ3Y

5 Nov 2026, 21:01 UTC455 viewsread 11 November 2026

🛒 Корзина товаров на чистом JavaScript — [1:06:48] В этом видео, на основе готовой страницы на HTML и CSS, вы сможете создать стандартную корзину с товарами, которую обычно встречаете в интернет-магазинах. Учтите, что вам не обязательно создавать такую же вёрстку, как у автора видео, ведь этот UI-компонент вы без проблем сможете интегрировать в любую другую страницу. Перейти к просмотру

3 Nov 2026, 20:27 UTC517 viewsread 11 November 2026

⚙️ Делаем уведомления на JavaScript В этом практическом уроке вы сможете написать свою JS-библиотеку для создания всплывающих уведомлений трёх разных типов. Автор показывает не только процесс написания JavaScript-кода, но ещё и с нуля верстает макет уведомлений, что особенно полезно, если вы хотите сами повторить что-то подобное в своем проекте. https://youtu.be/515ZqLisbyc

1 Nov 2026, 20:57 UTC560 viewsread 11 November 2026

🧠 О чём спросить компанию на IT-собеседовании — [20:01] Почему-то принято думать, что при собеседовании только компания задаёт вопросы, но это не совсем так. Если у будущего сотрудника нет никаких вопросов о компании, то это может стать серьёзным звоночком для того, чтобы не принять его на работу. Поэтому, в этом видео автор рассказывает, какие вопросы айтишнику стоит задавать на собеседовании, чтобы и получить выг…

31 Oct 2026, 20:28 UTC557 viewsread 11 November 2026

🐍 Весь Python за 7 часов Ну, почти весь. Несмотря на то, что Python — это мегапростой язык, справиться с освоением которого сможет даже ребёнок, у него есть целая куча особенностей. Они, вперемешку с обычной теорией (которой здесь предостаточно), как раз-таки и разбираются в этом видео. Понятное дело, что профессионалом за эти 7 часов вы явно не станете, но после просмотра вы уже уверенно сможете писать простенькие…

30 Oct 2026, 20:00 UTC530 viewsread 11 November 2026

Автоматизация тестирования с Pytest и Python В уроках автоматизации тестирования, мы будем создавать проект с нуля используя самые популярные технологии на данный момент для автоматизации на Python. 📂 Перейти к курсу

29 Oct 2026, 20:48 UTC544 views3 reactionsread 11 November 2026

Алиасы в GIT Большинство из нас знают, что такое GIT. При этом большинство из тех, кто им пользуется, постоянно применяют, по сути, одни и те же команды. Например: git status git commit -m 'commit' Git позволяет создавать алиасы команд. Благодаря этому вы можете вводить не длинную строку команды, а ее короткий псевдоним. Создаём alias: git config --global alias.st status git config --global alias.cm 'commit -m'…

❤3

28 Oct 2026, 20:30 UTC516 viewsread 11 November 2026

📖 В чем смысл open source? Многие слышали про open-source разработку, но немногие понимают, в чём вообще прикол всего этого. Ещё сложнее осознать, что с некоторыми программистами такого случилось, что они готовы писать код за бесплатно. О том, почему они это делают, выставляя при этом код на общественное обозрение, а также почему компании сами делают свои проекты опен-соурсными — в этом коротком видео. https://you…

27 Oct 2026, 20:33 UTC538 viewsread 11 November 2026

⌨️ 14 очевидных признаков плохого кода Если вы не хотите испытывать желание провалиться под землю каждый раз, когда ваш код читает кто-то другой, то вы, как разработчик, просто обязаны писать свой код просто и понятно. В этом видео автор представил собственный список из 14 правил адекватного кода, с которым точно не поспоришь. Если вы хотите стать по-настоящему плохим программистом, тогда ни в коем случае их не соб…

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

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.

Коэффициент Продуктивности
@productivity_Q · 26,511
Telegram ranks this channel #15 of 84 here — alongside 83 others — read 12 September 2026
Книжное хранилище
@knijnoe_xranilishe · 19,509
Telegram ranks this channel #19 of 73 here — alongside 72 others — read 30 September 2026
TechNews
@techlucker · 42,607
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 28 August 2026
[404] — программирование
@procode404 · 40,080
Telegram ranks this channel #32 of 83 here — alongside 82 others — read 30 August 2026
Senior Java Developer
@seniorjavist · 20,368
Telegram ranks this channel #36 of 89 here — alongside 88 others — read 26 September 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
Telegram ranks this channel #45 of 90 here — alongside 89 others — read 2 October 2026
Senior Python Developer
@seniorpy · 39,134
Telegram ranks this channel #47 of 92 here — alongside 91 others — read 30 August 2026
Windows Community
@wind_community · 40,852
Telegram ranks this channel #61 of 74 here — alongside 73 others — read 29 August 2026

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

“Заметки программиста” (@progersbooks), 8,120 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/progersbooks.

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.