Channel
@code_cleanup
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002506505109 |
|---|---|
| Type | Channel |
| Username | @code_cleanup |
| Created | 19 April 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/code_cleanup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 00:31 | 14 | no change |
| 6 Aug 2026, 18:03 | 14 | first reading |
6 posts held, back to 19 April 2025 — 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 16 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
14 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 6 | 42.9% | |
| ❤ | 4 | 28.6% | |
| 👍 | 4 | 28.6% |
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 4 of the 6 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 19 April 2025 to 16 April 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.
Привет, а вот и новое видео! В прошлой серии мы залезли в одну функцию сортировки и улучшали её. В этот раз смотрим шире — почему так больно работать с компонентом и откуда берутся данные. А конкретно: — выносим бизнес-логику из React компонента — разбираемся с концепцией derived state — используем селекторы в Zustand — пишем тесты 💚 на стор без React и DOM — и даже ловим классическую ошибку с getSnapshot в Next.js…
🔥4👍1
Неужели мы выпустили видео? Конечно выпустили! Ну и шляпу там нам AI нагенерил, сортировка пузырьком. Рефакторим по TDD, максимально упрощая логику. Объясняем, в чём прикол разных локалей при сортировке. Улучшили качество видео. Пока мы ещё не супер-блоггеры, но стремимся! Энджой, лайк, подписка https://youtu.be/rTbZ38qX_6Q
❤4
Привет! Нам указали, что в эпизоде #1 мы забыли добавить ref для form, хотя используем его в коде. Исправили свою ошибку в этом пулреквесте. Мы не заметили это в процессе записи потому что начиная с React 19.1 ref вовсе не нужен. Форма сама очищается после отправки. Спасибо, что внимательно смотрите ♥️
👍3
Смотрите наш первый эпизод! Разбираемся, как избавиться от useState в формах с помощью новых фишек React 19, и обсуждаем, когда это не прокатит. Постарались, чтобы было не слишком затянуто, но при этом понятно. Получилось? Расскажите в комментариях! https://youtu.be/JdMGSgh9uHA
🔥2
Всем привет! Мы — Алекс и Алёна делаем видеоподкаст про рефакторинг. У нас 20+ лет во фронтенде на двоих, и мы решили делиться опытом на youtube. Алёна: я senior frontend developer, тимлид Доки, автор, переводчик, спикер, эдьюкейтор. Работаю как с экосистемой React и Next.js, так и с vanilla-стеком. Мой опыт в образовании помогает нам объяснять вещи простым языком. Алекс: я senior software engineer, бывший яндексои…
Channel created
Showing the 6 most recent of 6 posts we hold for @code_cleanup. 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“code_cleanup” (@code_cleanup), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/code_cleanup.
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.