2 measurements spanning 1 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 119–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 04:02
120
no change
7 Aug 2026, 16:15
120
first reading
Engagement
11 posts held, back to 23 February 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 pageof 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 11 posts for this entry, the most recent from 28 March 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
30
Videos
6
Links
11
Lifetime counters from Telegram’s own channel header, read 9 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.
Video runtime
1m 08s
Average length
23s
Measured directly from 3 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
103 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 63.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
65
63.1%
❤
22
21.4%
👍
16
15.5%
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 10 of the 11 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 11 most recent posts we hold, published 23 February 2025 to 28 March 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 11 we hold a reading for · 9%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @channel_under_development. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 11 most recent posts we hold for this entry, published 23 February 2025 to 28 March 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
❓Используете ли вы подход test-driven development (TDD) на практике? Приносит ли пользу эта методология или только усложняет разработку?
Привет! Это Фёдор Турков, старший Android-разработчик в группе мобильных приложений «Главная, ЛК и Маркетинг» и автор канала в разработке. Я использую TDD, хоть и не так часто, как хотелось бы. Мой опыт — в комментариях, ваши ответы буду ждать там же ⬇️
#ozontech_вопросы
#compose
Modifiers в Jetpack Compose
😀 Инструмент для настройки внешнего вида и поведения элементов
😀 Меняет размеры, отступы, выравнивания(size, padding, aligment)
😀 Добавляет клики, скролл и т.д. (clickable, vertical/horizontalScroll)
😀 Настраивает accessibility(semantics)
😀 Устанавливает background, делает clip и все в этом духе
😀 На самом деле их очень много, проще почитать доку и пощупать самому
😀 На что можно…
Жаркая прошлая #неделька. Выдалась очень насыщенной. Или как я вспомнил молодость
😀 С кайфом поработал. Уже какое-то время делаю задачку с приколами, с которыми ранее не имел дел. В общем, все почти стандартно, но было над чем подумать
😀 Попробовал заюзать chain of responsibility, выглядело классно, но как только стало нужно сделать другую реализацию, вся польза рассыпалась. Шишку набил, запомнил
😀 Ещё посетил Моби…
#Неделька за две. Куда-то я пропал. Сгонял в отпуск, который плавно перетек в больничный
😀 Сгоняли на горнолыжку "Банное"
😀 Успели очень хорошо. С каждым днём снег таял все больше и появлялись проплешины на трассах
😀 Вспомнили как катать и даж подняли скилл, стали ещё увереннее
😀 Покатали в облаках, в тумане, по мокрому снегу, по лужам, немного по земле, в дождь, в ветер, в солнечную погоду
😀 На видосиках и фотос, м…
#compose
Lifecycle of composables: продолжение и завершение по ЖЦ. Что compose пропускает, а что перерисовывает
😀 Пропускает, если тип в состоянии является стабильным и оно не изменилось. Стабильными считаются либо примитивы, либо классы помеченные аннотацией @Stable
😀 Не пропускает, если функция: возвращает тип отличный от Unit, помечена аннотацией @NonRestartableComposable или @NonSkippableComposable, принимает в …
#compose
Ещё несколько приколов с местом вызова composable-функции
😀 Kotlin позволяет нам вызывать функции в цикле и тогда получается, что у них одно место вызова
😀 В этом случае Compose учитывает порядок вызова и все будет окей, если при рекомпозиции новые элементы будут добавлены в конец. Новые нарисуются, а старые не будут затронуты
😀 А вот если в середину или в начало, то меняется порядок и Compose больше не мож…
#compose
Как обещал, пример и что-то типо его разбора для предыдущего поста, все из доки. Смотрим следующий фрагмент кода:
@Composable
fun LoginScreen(showError: Boolean) {
if (showError) {
LoginError()
}
LoginInput()
}
😀 Есть у нас функция, которая рисует ошибку логина и функция, которая рисует поле ввода для логина
😀 При этом, если состояние без ошибки, то ошибка не рисуется, а поле ввода рису…
#compose
Lifecycle of composables: тут мы должны будем узнать про жизненный цикл(ЖЦ) функции и про то, как Compose решает, нужна ли рекомпозиция
😀 Короче, если пройтись по верхам, то все изи
😀 ЖЦ проще, чем у вьюх. Есть вход в композицию, есть выход из композиции и между ними от 0 до n рекомпозиций
😀 Если нам надо использовать ЖЦ чего-то над composable-фунциями, то надо заюзать эффекты, но это мы ещё не знаем — отде…
Ещё одна, по ощущениям, очень быстро прошедшая #неделька
😀 Разбирался с очередным незнакомым местом в проекте, чтобы реализовать часть новой фичи
😀 Вроде разобрался, что-то даже заработало, останется перепроверить и навести красоту в коде
😀 Теперь про зубки. Писал, что терпимо, а через минут 15 чуть не откинулся от боли, когда заморозка отошла
😀 Но все не так страшно, закинул обезбол и отпустило, покушал и лег спат…
И снова здравствуйте, шо очередная #неделька пройдена, достаточно насыщенная
😀 По работе все по кайфу. И кодик писал, и контракты создавал
😀 Даже выбрался в офис в пятницу, фотос на месте, поймал красивый закат
😀 В эту же пятницу сгонял на митап, хорошечно провели время, послушали докладики, пообщались и завершили все это дело баром, фотос с митапа тоже на месте. И запись уже есть ВК, YouTube
😀 Сегодня попрощался с…
🔥5❤1
Showing the 11 most recent of 11 posts we hold for @channel_under_development. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 11 most recent posts we hold, published 23 February 2025 to 28 March 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@channel_under_development named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@nonskippablecomposable named in 1 post, 10 August 2026 – 10 August 2026
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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“Канал в разработке” (@channel_under_development), 120 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/channel_under_development.
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.
