Telegram RegisterThe public register of Telegram

Channel

Борода бывшего программиста

@ex_coder_tsarev

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

208subscribers

+0 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-1001652074809
TypeChannel
Username@ex_coder_tsarev
DescriptionСейчас рук. направления в Озоне, ранее директор по разработке idp.zyfra.com leotsarev.ru t.me/leotsarev Много ссылок на статьи и нытья
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/ex_coder_tsarev

Growth

2087 Aug 2026, 14:13 — 208 subscribers8 Aug 2026, 11:05 — 208 subscribers7 Aug 2026, 14:138 Aug 2026, 11:05
2 measurements taken within a single day. 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 207–209 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:05208no change
7 Aug 2026, 14:13208first reading

Engagement

20 posts held, back to 16 March 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
76.9%
avg views ÷ 208 subscribers
Avg views / post
160
1 post measured
Reaction rate
10.0%
reactions ÷ views · ER floor
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 July 2026
Posts held20 (16 March 202620 July 2026)
Views total160
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:05 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
55
Links
143

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

171 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 22.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3922.8%
😁3218.7%
👍2313.5%
🤣169.36%
148.19%
95.26%
💯95.26%
👀63.51%
😱63.51%
🤬63.51%
😢42.34%
🫡42.34%
👏31.75%

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 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 171reactions 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 16 March 2026 to 20 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.

Recent posts

20 Jul 2026, 08:43 UTC160 views16 reactionsread 8 August 2026

Железная Женщина, ЖЖ — робоголос, сообщающий о срабатывании алерта в Озоновской внутренней системе алертинга (самописный аналог Sentry). Железная Женщина достаточно смела, чтобы не давать спать кому угодно. Телефон Железной Женщины добавлен в белые списки «что трезвонило среди ночи» наравне с телефоном жены и дочери. У большинства руководителей на Железную Женщину свой персональный звонок, поэтому посреди совещания т

🔥14🤣1😁1

13 Jul 2026, 09:49 UTC255 views2 reactionsread 8 August 2026

https://t.me/the_good_question/106 Правила использования ИИ в работе (гуманитарной) #дедосваиваетии

👍2

29 Jun 2026, 09:33 UTC346 viewsread 8 August 2026

Джуны тут не для того, чтобы закрывать задачки в Джире https://newsletter.kentbeck.com/p/hey-n00b-we-didnt-hire-you-to-complete

22 Jun 2026, 11:51 UTC398 views5 reactionsread 8 August 2026

https://news.ycombinator.com/item?id=48568502 HTTP QUERY Новый глагол. С семантикой GET но телом как у POST

😱5

17 Jun 2026, 07:23 UTC460 views9 reactionsread 8 August 2026

https://t.me/natalya_kasperskaya_channel/274 Помимо повестки про телегу и VPN, за которую полагаю все зацепятся, там написано важное: Технари не должны безмолвно делать хуйню со ссылкой на заказчика. Часто говорят, что «людей, кто работал в РКН никто потом не наймет». И это, наверное будет заслуженно. Но не за то, что «блокировать телеграмм плохо». А за то, что они взялись блокировать телеграмм и не смогли. И скор

8🔥1

9 Jun 2026, 15:28 UTC558 views8 reactionsread 8 August 2026

6 июня 2026 года Let's Encrypt включил в свой terms of service: You are not a person or entity that is: > (a) located in, organized under the laws of, or ordinarily resident in any country or territory that is the target of comprehensive U.S. sanctions; В общем, полагаю, массовый отзыв сертификатов LE в России не за горами. Есть ли альтернативы?

🤬6😢2

8 Jun 2026, 08:33 UTC355 views20 reactionsread 8 August 2026

«Теперь поищу в коде строки, которые могут быть секретами, например, "password=", "secret=". Использую grep с регулярным выражением. Но чтобы не тратить время, отмечу пункт как выполненный.» #дедосваиваетии

😁20

1 Jun 2026, 07:41 UTC407 views7 reactionsread 8 August 2026

С интересом смотрю на параллели ремонт и разработка ПО. Тут в целом все те же стадии: говоришь, что тебе нужно, потом происходит оценка сроков и денег, потом ты коммитишься, потом начинается работа потом сроки проябываются, а деньги растут. Действуют те же правила, что и в программировании. Например, нужно объяснять заказчику в чем состоит выбор, и таким образом переносить ответственность на его сторону. Но вот с

🔥43

25 May 2026, 09:58 UTC372 views8 reactionsread 8 August 2026

Мой незабвенный начальник в Фортисе (а позже коллега в ЦИП) Антон З любил (к его чести, скорее в шутку) приговаривать «надо все успевать». В реальности успевать все невозможно, и есть приоритеты. Если ты говоришь своим подчиненным «все приоритетно», то ты как будто отказываешься управлять их приоритетами. В какой-то степени это тоже хорошо в рамках #месячникборьбысмикроменеджментом, но имеет свои минусы. Хочется нап

💯71

18 May 2026, 08:03 UTC446 views11 reactionsread 8 August 2026

В рамках месячника борьбы с микроменеджментом приказываю: «Каждому руководителю проверить каждую встречу своих подчинённых за ближайшие три недели в поисках проявлений микроменеджмента». (Это был контент для @ProductBalance) #месячникборьбысмикроменеджментом

🤣6🫡4😱1

29 Apr 2026, 08:56 UTC497 views10 reactionsread 8 August 2026

Признание реальности — принцип построения ИТ Озона, согласно которому физика всегда побеждает систему (о различиях между этими понятиями см https://t.me/ex_coder_tsarev/280). Если какой-то предмет находится физически в том месте, куда он никак не мог попасть по системе, то система все равно обязана этот кейс отработать, признать реальность (то есть исправить системный статус согласно физическому) и предложить пользо

🔥10

22 Apr 2026, 08:03 UTC400 views16 reactionsread 8 August 2026

Жирный палец — действие пользователя (тут: работника Озона) в котором пользователю легко ошибиться, поэтому ИТ-система не вправе полагаться на него, как на безвозвратное. Например, если курьер нажал своим жирным пальцем, что довез клиенту товар, это не значит, что это произошло физически — курьер мог отметить в приложении на бегу что-то не то (да банально попасть не в ту кнопку, отсюда «жирный палец») и система должн

👍10🔥4😁2

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

Mentions

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.

“Борода бывшего программиста” (@ex_coder_tsarev), 208 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ex_coder_tsarev.

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.