Telegram RegisterThe public register of Telegram
Telegram profile photo for Fedkin is thinking

Channel

Fedkin is thinking

@fedkin_thinking

On this record: Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry

7,919subscribers

-32 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002023739581
TypeChannel
Username@fedkin_thinking
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/fedkin_thinking

Growth

7,9197,9517,9356 August 2026 — 7,951 subscribers6 August 2026 — 7,951 subscribers8 August 2026 — 7,928 subscribers12 August 2026 — 7,926 subscribers15 August 2026 — 7,919 subscribers6 August 202615 August 2026
5 measurements spanning 9 days, net -32. 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 7,914–7,956 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:087,919-7
12 Aug 2026, 01:427,926-2
8 Aug 2026, 18:517,928-23
6 Aug 2026, 04:407,951no change
6 Aug 2026, 03:327,951first reading

Engagement

21 posts held, back to 21 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
53.7%
avg views ÷ 7,919 subscribers
Avg views / post
4,250
6 posts measured
Reaction rate
1.92%
reactions ÷ views · ER floor
Posts in window
6
of 21 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 8 August 2026
Posts held21 (21 February 20268 August 2026)
Views total25,510
Reactions total489
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:00 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.

Reaction mix

1,481 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 51.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍76751.8%
🔥52335.3%
💅664.46%
🤔533.58%
281.89%
😁221.49%
custom 536190916027325584090.608%
90.608%
🙏40.27%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 21 of the 21 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 1,481reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 21 February 2026 to 8 August 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
4
across the posts below
Posts paid on
2
of 21 we hold a reading for · 10%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fedkin_thinking. 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 21 most recent posts we hold for this entry, published 21 February 2026 to 8 August 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.

Recent posts

8 Aug 2026, 08:57 UTC≈2,430 views48 reactionsread 12 August 2026

Пару месяцев назад я ходил на конфу Тинька, посвященную в основном GenAI в поддержке В одном из докладов был интересный подход, как можно собирать контекст для агентов, если он разбросан по куче разных мест (в т.ч. головам людей) — Проблема формулируется примерно так: операторы поддержки отвечают пользователем на основе базы знаний. Но... много контекста живет еще в каких-то левых пдфках, чатах, таблицах, неявных

🔥38💅7👍3

2 Aug 2026, 07:31 UTC≈3,810 views44 reactionsread 12 August 2026

Первый шаг к хорошей техностратегии Команда упорно работала 3 месяца и подняла аптайм системы с 99.9% до 99.99%, перепилив архитектуру сервиса, из-за которого еженедельно падали на 10 минут. Молодцы конечно, а это точно кому-то было нужно? Вполне может оказаться, что бизнесу было ок и с этим 10минутным даунтаймом и "ваще на че вы потратили 3 месяца???" — Любая система обладает набором свойств: надежность, секьюрн

👍309🔥4💅1

1 Aug 2026, 18:30 UTC≈3,750 views37 reactionsread 12 August 2026

Продукт, тех и взаимопонимание Уверен, все были свидетелями обсуждений где продакт говорит про пользовательский путь, ценность и сроки, а разработка про какие-то мистические "сущности", апишки и очереди. Вроде все всё правильно говорят, но чето обсуждение не двигается На помощь приходят хорошие практики типа ubiquitous language, event storming, user story mapping, ... ... и прототипирование. Год назад я писал пост

👍293🔥3custom 53619091602732558402

22 Jul 2026, 07:13 UTC≈5,640 views45 reactionsread 12 August 2026

У меня иногда возникает желание почитать что-то эдакое забористое про бэкенд И если бы меня попросили порекомендовать что-то русскоязычное по теме, я бы порекомендовал канал Лёши Рыбака (многие из вас его знают по курсам по сисдизу devhands) Леша делает классные разборы: - PostgreSQL на 800млн пользователей от OpenAI — что с ним не так https://t.me/rybakalexey/402 - SPDY, QUIC, HTTP/2 и HTTP/3: кратко: https://t.me

🔥199😁9👍7💅1

18 Jul 2026, 13:20 UTC≈5,660 views84 reactionsread 12 August 2026

Длиннопост про сон 50 реакций набрали оч быстро, поэтому ловите! Важное уточнение: причиной плохого сна могут быть конкретные заболевания • апноэ • синдром беспокойных ног • гормональные сдвиги / дефициты витаминов Поэтому по-хорошему сначала надо сходить к врачу и удостовериться, что у тебя с этим все норм Далее речь про мой опыт. Показатели сна трекаю кольцом oura, неплохо отражает реальную картину Низкое влия

🔥61👍173💅1🤔1custom 53619091602732558401

18 Jul 2026, 12:01 UTC≈4,220 views231 reactionsread 12 August 2026

Есть простая ловушка, в которую легко попасть, если тебе нравится твоя работа - начать слишком сильно в нее вкладываться и забивать на остальное Пока всё получается - кайф, ты растешь, получаешь постоянное позитивное подкрепление, вкладываешься еще больше Но как только начинаются первые проблемы, мозгу начинает казаться мол вся жизнь говно. И формально это правда, если работа занимает большую часть жизни Поэтому в

🔥2069👍6💅6🙏31

12 Jul 2026, 18:23 UTC≈5,780 views59 reactionsread 12 August 2026

Как чуть меньше страдать от нейрослопа Или небольшой полезный тех, который ты можешь сделать за пару дней Давеча я писал, что агенты без должного контекста о системе склонны к локально оптимальным решениям. Это часто приводят к: • нарушению направления зависимостей в коде • смешиванию доменной логики и инфраструктурной • странному неймингу и расположению классов Хорошая новость — многое из этого можно ловить детер

👍54🔥2custom 53619091602732558402🤔1

4 Jul 2026, 15:04 UTC≈6,920 views52 reactionsread 12 August 2026

Несколько избитая тема, но мне кажется очень красивой идея, которая стоит за structured output в современных ллмках Задача — пользователь передает json-схему, нужно сгенерировать ответ строго по переданной схеме 1. Наивный вариант Подложить схему в контекст: ... Return a JSON object that strictly matches the following schema: { "type": "object", "properties": { "status": { "enum": ["SUCCESS", "FAI

👍38🤔8🔥41💅1

4 Jul 2026, 13:10 UTC≈5,100 views61 reactions3 Starsread 12 August 2026

Если ты слишком хорошо решаешь проблемы — возможно, ты решаешь не те Пост по мотивам одного из худших полугодий на работе:) Когда всё вокруг горит, мы начинаем преувеличивать значимость каждой конкретной проблемы. Каждая проблема кажется той самой, что нужно решить прямо сейчас. Естественная реакция на такое — сделать хоть что-то, что продвинет ситуацию вперед • Команды не договорились — синхронизировать • Сроки е

👍50🔥6💅41

7 Jun 2026, 12:29 UTC≈7,670 views135 reactionsread 12 August 2026

Очень грубо инженеров можно классифицировать на два типа: 1. Те, кто работает с техническими проблемами проактивно: • Увидел плавное повышение cpu usage на БД => раздебажил из-за чего, добавил нужных индексов, предотвратил инцидент • Увидел, что новая функциональность в модуль добавляется очень странным образом => инициировал и довел до конца рефакторинг, благодаря этому крупный проект сошелся в срок • Сделал удобны

👍110🔥19🤔5💅1

30 May 2026, 14:11 UTC≈7,630 views46 reactionsread 12 August 2026

Разработка фичей без достаточной экспертизы в системе зачастую превращается в набор "локально-оптимальных" решений: здесь добавили ифчик, здесь протянули новую зависимость, здесь скопипастили похожий код, здесь обошли существующую точку расширения Каждое такое решение обычно выглядит норм в моменте — оно закрывает задачу, проходит тесты, не выглядит совсем плохо на ревью Проблема начинается, когда такие решения пос

👍43💅3

12 May 2026, 15:02 UTC≈8,560 views16 reactionsread 12 August 2026

Как сделать карьерный рост чуть приятнее Чем выше роль, тем меньше работа про сами задачи и тем больше — про людей. Всегда кто-то что-то требует, кто-то не согласен, кто-то аккуратно тянет одеяло на себя. Кто-то заходит в разговор так, что выходишь после него с ощущением, будто из тебя высосали всю энергию Но, на самом деле, в таких сложных разговорах у разных людей одни и те же паттерны — тебя уводят от сути разго

💅9😁5👍2

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

5 Apr 2026, 09:56 UTCAnonymous Poll1,010 voters approx.

Какой у вас Cycle Time в команде? Время от взятия в работу до выкатки в прод типичной продуктовой задачи

  1. < 1 дня3%
  2. 1-3 дней12%
  3. 4-6 дней19%
  4. 7-14 дней34%
  5. 14+ дней32%

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 21 most recent posts we hold, published 21 February 2026 to 8 August 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.

Citation-graph rank

Citation-graph rank — 9,978 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — 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.

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Fedkin is thinking” (@fedkin_thinking), 7,919 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/fedkin_thinking.

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.