Channel
@isqualog
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
587subscribers
-1 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001005964091 |
|---|---|
| Type | Channel |
| Username | @isqualog |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/isqualog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 17:25 | 587 | -1 |
| 19 Aug 2026, 02:34 | 588 | -1 |
| 12 Aug 2026, 02:42 | 589 | +1 |
| 6 Aug 2026, 18:02 | 588 | no change |
| 5 Aug 2026, 22:05 | 588 | first reading |
16 posts held, back to 3 October 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 16 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
231 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 34.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 79 | 34.2% | |
| ❤ | 52 | 22.5% | |
| 👍 | 49 | 21.2% | |
| 😁 | 40 | 17.3% | |
| 🤔 | 8 | 3.46% | |
| 😱 | 2 | 0.866% | |
| 👎 | 1 | 0.433% |
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 16 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 231 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 3 October 2025 to 24 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @isqualog. 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 16 most recent posts we hold for this entry, published 3 October 2025 to 24 July 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.
Диктовка На работе нам раскатили Wispr Flow — аппка для распознавания речи в любом текстовом поле. Ставишь курсор в слак тред, зажимаешь Fn и надиктовываешь, а он за тебя печатает. На этой волне я решил и в айфоне чаще пользоваться встроенной диктовкой, ну где микрофончик у клавиатуры нажимаешь. И то ли у меня с дикцией чё-то не то, то ли я натолкнулся на парадигму «сначала ориентируем продукт в США, а потом может…
😁9👍1
Видели уже страничку с пулреквестами в гитхабе? Я только сегодня обнаружил редизайн, обычно как-то захожу в конкретную репу свои PR смотреть. Удобно в целом! https://github.com/pulls/inbox
пожалуйста уберите огонёчек, и так жарко
😁17🔥13
Европу накрыла heat wave, поэтому сегодня у нас рубрика РАСПАКОВКА В Германии кондиционеры делают, но не устанавливают. Как охлаждаться? Сгонял в аптеку и магаз, купил: 1. Охлаждающий гелевый пакет (справа снизу). В морозилку его, он замерзает, потом кладёте на голову или куда вам там надо 2. Пакет гипотермический одноразовый (большой белый). На экстренный случай, если уходите куда-то или холодильник помер. Для ис…
❤15🔥11😁6🤔1
Жизнь научила меня не смешивать разные изменения в одном PR Фичи, багфиксы, рефакторинг — у этих изменений разный контекст и разный уровень риска. Бывает, сядешь за новую фичу, и видишь, отрефакторить бы немного, тогда фича отлично ляжет. Ну рефачишь, по дороге еще какой-то баг обнаружил в соседней фиче, его поправил, заливаешь пулрик на 1к строк с этим всем. В чём проблема? Сложно одновременно всё ревьюить (разные…
🔥6❤4
Привет, а вот и новое видео! В прошлой серии мы залезли в одну функцию сортировки и улучшали её. В этот раз смотрим шире — почему так больно работать с компонентом и откуда берутся данные. А конкретно: — выносим бизнес-логику из React компонента — разбираемся с концепцией derived state — используем селекторы в Zustand — пишем тесты 💚 на стор без React и DOM — и даже ловим классическую ошибку с getSnapshot в Next.js…
🔥5❤2
Layers vs Vertical Slices Кирилл Мокевнин (Hexlet) набросил, как файлы класть — по типу или по домену? Для меня меня на фронтенде это вопрос давно решенный: если сервис больше чем 2 странички, то, конечно, по фичам. Иначе, чтобы поправить какую-то мелочь, надо по 5 папкам лазить. 📗 Главный принцип: low coupling, high cohesion Недавно был на проекте: 90к строк кода, 4 фронтендера. Код разложен по слоям: consts, ut…
🔥12❤2
Структура файлов на проекте, импорты, barrel файлы. Пост ниже ↓
🤔1
Неужели мы выпустили видео? Конечно выпустили! Ну и шляпу там нам AI нагенерил, сортировка пузырьком. Рефакторим по TDD, максимально упрощая логику. Объясняем, в чём прикол разных локалей при сортировке. Улучшили качество видео. Пока мы ещё не супер-блоггеры, но стремимся! Энджой, лайк, подписка https://youtu.be/rTbZ38qX_6Q
❤10👍2🔥1
Мифы про отличия Zustand и Redux Работаю сейчас с zustand, который уже обогнал redux по загрузкам. Вот что говорят адепты zustand, сравнивая его с redux: Миф 1: В Zustand можно создавать множество сторов вместо одного! По факту и правда можно, но в доке Zustand советуют «single store». А если мол ваше приложение большое, можете разделить стор на слайсы. В redux тоже single store, который можно разделить на слайсы…
❤8🔥7🤔4😱2👎1
Photo, posted without a caption
🤔1
Толщина рамок в уголках 10+ лет в индустрии, и вот снова неделю крашу кнопки. Файн-тюним дизайн-систему на проекте. Знаете же эти модные кнопки и плашки с градиентными рамками? Обычно это два элемента: «задний» с градиентным фоном выглядывает из-за «ближнего» элемента с белым фоном (ну или какой там фончик). Если делать одинаковый border-radius у внутреннего и внешнего элемента, то уголки как бы утолщаются, выгляд…
👍16😁6🔥3
Showing the 12 most recent of 16 posts we hold for @isqualog. 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.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“isqualog • front-end • productivity” (@isqualog), 587 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/isqualog.
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.