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

Channel

Fedkin is thinking

@fedkin_thinking

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Polls · Citations · Telegram's recommendations · Cite this entry

8,826subscribers

+875 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
DescriptionСотрудничество: @qsqnk
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 live11 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/fedkin_thinking

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

7,8969,1268,5116 August 2026 — 7,951 subscribers6 August 2026 — 7,951 subscribers8 August 2026 — 7,928 subscribers12 August 2026 — 7,926 subscribers15 August 2026 — 7,919 subscribers17 August 2026 — 7,896 subscribers21 August 2026 — 7,898 subscribers24 August 2026 — 8,023 subscribers28 August 2026 — 8,802 subscribers31 August 2026 — 8,937 subscribers3 September 2026 — 9,110 subscribers8 September 2026 — 9,126 subscribers12 September 2026 — 9,087 subscribers16 September 2026 — 9,047 subscribers25 September 2026 — 9,010 subscribers4 October 2026 — 8,919 subscribers10 October 2026 — 8,912 subscribers14 October 2026 — 8,898 subscribers17 October 2026 — 8,877 subscribers20 October 2026 — 8,846 subscribers23 October 2026 — 8,831 subscribers26 October 2026 — 8,820 subscribers30 October 2026 — 8,841 subscribers2 November 2026 — 8,848 subscribers5 November 2026 — 8,850 subscribers8 November 2026 — 8,843 subscribers11 November 2026 — 8,826 subscribers8,8266 August 202611 November 2026
27 measurements spanning 98 days, net +875. 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,712–9,311 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
11 Nov 2026, 21:178,826-17
8 Nov 2026, 07:008,843-7
5 Nov 2026, 05:398,850+2
2 Nov 2026, 07:098,848+7
30 Oct 2026, 01:488,841+21
26 Oct 2026, 21:068,820-11
23 Oct 2026, 11:368,831-15
20 Oct 2026, 15:388,846-31
17 Oct 2026, 15:588,877-21
14 Oct 2026, 09:518,898-14
10 Oct 2026, 23:578,912-7
4 Oct 2026, 23:428,919-91
25 Sept 2026, 17:599,010-37
16 Sept 2026, 16:589,047-40
12 Sept 2026, 17:409,087-39
8 Sept 2026, 13:599,126+16
3 Sept 2026, 06:149,110+173
31 Aug 2026, 04:238,937+135
28 Aug 2026, 00:548,802+779
24 Aug 2026, 18:538,023first reading

Engagement

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

ERR · 30 days
50.3%
avg views ÷ 8,826 subscribers
Avg views / post
4,440
10 posts measured
Reaction rate
0.98%
reactions ÷ views · ER floor
Posts in window
10
of 45 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 15 November 2026
Posts held45 (21 February 2026 – 15 November 2026)
Views total44,390
Reactions total435
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 03:45 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
21
Links
67

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

2,972 reactions across 44 posts, in 10 distinct kinds. The most used accounts for 43.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,29543.6%
🔥79426.7%
❤31310.5%
😁2799.39%
💯1244.17%
💅802.69%
🤔531.78%
✍150.505%
🙏100.336%
custom 536190916027325584090.303%

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 is Telegram’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 45 of the 45 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 2,972 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 45 most recent posts we hold, published 21 February 2026 to 15 November 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 45 we hold a reading for · 4%
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 45 most recent posts we hold for this entry, published 21 February 2026 to 15 November 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

Telegram’s own ‘edited’ marker: 3 of 10 posts held from the last 30 days (30.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 11:53 UTC≈2,310 views40 reactionsread 17 November 2026

215 files changed, 7493 insertions(+), 3489 deletions(-) Простите за ПТСР На самом деле, с агентским кодингом начал чаще видеть такую схему: Чем больше и непонятнее PR → тем сильнее "на отвали" его смотрят → тем сильнее размывается архитектура → тем больше и непонятнее очередной PR Повторить. Бороться с каждым отдельным PR-ом достаточно бессмысленно. Нужно выстраивать архитектуру, в которой агент будет делать из…

🔥32👍7💅1

14 Nov 2026, 09:50 UTC≈2,540 views26 reactionsread 17 November 2026

Красивое https://ivangsa.com/articles/sdd-from-event-storming-to-a-model-your-agents-can-read/ Ребята предлагают делать спеки для Spec-Driven-Development через концепции Event Storming и DDD: domain event, command, policy и вот это всё Это подступается к двум проблемам, которые есть в классической схеме, где спеки — это только набор md-шек: • Из сотни исторических md-шек сложно собрать общую картину, кто с кем как…

🔥16👍6❤3✍1

11 Nov 2026, 07:53 UTC≈3,430 views26 reactionsread 17 November 2026

Кто просил запись нашего с Андреем стрима о карьерных целях, ловите! https://youtu.be/TZnZN-u3bw8 Таймкоды: 00:00 Вступление и ожидания от стрима 03:42 Знакомство со спикерами 08:01 Что такое карьера? 12:25 Зачем нужны карьерные цели? 17:32 Как работа соотносится с жизненными целями? 22:17 Карьерные цели на разных этапах жизни и работы 33:59 Как понять свои потребности и выбрать направление 36:33 Личные цели проти…

🔥15👍9❤2

4 Nov 2026, 16:10 UTC≈4,620 views20 reactionsread 17 November 2026
Photo

Больше ответственности — а мне это зачем? Допустим, тебе предлагают залидить новый проект. Больше людей, больше внимания руководства, сложные вызовы. Звучит как карьерная возможность Но если ты хотел больше зарабатывать — этот проект приблизит тебя к повышению? Или проще сменить команду/компанию? Если хотел глубже разобраться в технологиях — полезнее залидить проект самому либо взяться за его самую сложную техничес…

❤11👍5🔥4

4 Nov 2026, 13:10 UTC≈4,190 views33 reactionsread 17 November 2026

Два принципа проектирования непонятных штук 1. Идти от потенциальных блокеров и пытаться сделать на них PoC В сложных проектах всегда есть набор потенциальных причин, почему может не взлететь. Надо как можно раньше брать эти потенциальные причины и проверять их Например, вы делаете агента для автоматизации какого-то массового процесса. Можно сразу взять условный Qwen 27b, на котором будет работать прод, тюнить на …

👍27❤6

28 Oct 2026, 08:25 UTC≈5,090 views57 reactionsread 17 November 2026

А то ли я делаю? Представь, что ты единственный кто глубоко разбирается в какой-то замудренной системе/процессе. Все сложные вопросы и решения идут через тебя, без тебя почти ничего не происходит Можно начать активно учить остальных, писать документацию, делегировать. Через какое-то время система сможет нормально жить без тебя Это хороший результат? • если хочешь освободить время для новых задач — да • если хочеш…

🔥39👍9❤6💅3

19 Oct 2026, 16:58 UTC≈5,570 views61 reactionsread 17 November 2026

Если без шуток, то разница между "я подумал и решил, что вот это важно" и "я окнул то, что предожила нейронка" — ОГРОМНАЯ Окнуть правдоподобное нечто требует сильно меньше ментальных усилий Пожалуйста, не делайте так в важных решениях!

💯44❤8👍6😁3

19 Oct 2026, 16:50 UTC≈5,450 views100 reactionsread 17 November 2026

"Мы теперь пишем ADR на крупные архитектурные решения: сравниваем варианты, расставляем баллы. Всё обосновано" — А почему вот тут такие критерии сравнения? — Ну эйайка предложила

😁79💯17👍4

18 Oct 2026, 19:47 UTC≈5,660 views32 reactionsread 17 November 2026

^если вы вдруг не обновили версию телеги, то там статейка p.s.: это был один из самых болезненных опытов взаимодействия с телеграмом..

😁32

18 Oct 2026, 19:43 UTC≈5,530 views40 reactionsread 17 November 2026

Posted without readable text

🔥23👍10❤5😁2

4 Oct 2026, 07:50 UTC≈6,360 views68 reactionsread 17 November 2026

Недавно я готовил материал к тимлидской панельке, где одна из тем была про то, что команде иногда надо давать ошибаться И понял, что тема в общем-то актуальна не только для тимлидов Представь, что ты разработчик, который лучше всех разбирается в сервисе X. С высокой вероятностью большинство обсуждений "как лучше сделать" будут упираться в тебя. Изменится ли это со временем? С высокой вероятностью - нет:) —— Самые…

❤48💯13🔥4👍3

3 Oct 2026, 19:45 UTC≈5,850 views1 reactionsread 17 November 2026
Poll

Кто ты?)

  1. Разработчик бэка58%
  2. Разработчик фронта/мобилки2%
  3. Devops / SRE4%
  4. ML / DS2%
  5. Тимлид / техлид17%
  6. Архитектор4%
  7. Продакт / проджект2%
  8. Director / CTO4%
  9. тык (другое)8%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

❤1

Showing the 12 most recent of 45 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.

Posts recorded as deleted after publishing

We recorded 4 posts on @fedkin_thinking as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
4 November 2026
Most recent seen missing
15 November 2026
Median time before seen missing
18 days
Seen missing in the last 30 days
4

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

3 Oct 2026, 19:45 UTCAnonymous Poll1,820 voters approx.

Кто ты?)

  1. Разработчик бэка58%
  2. Разработчик фронта/мобилки2%
  3. Devops / SRE4%
  4. ML / DS2%
  5. Тимлид / техлид17%
  6. Архитектор4%
  7. Продакт / проджект2%
  8. Director / CTO4%
  9. тык (другое)8%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

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

Mentions

Named by 3 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Senior Java Developer
@seniorjavist · 20,341
Telegram ranks this channel #45 of 89 here — alongside 88 others — read 26 September 2026
Java библиотека
@javalib · 30,273
Telegram ranks this channel #56 of 84 here — alongside 83 others — read 7 September 2026
Golang
@Golang_google · 40,420
Telegram ranks this channel #59 of 90 here — alongside 89 others — read 30 August 2026
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 21,756
Telegram ranks this channel #62 of 88 here — alongside 87 others — read 21 September 2026
Библиотека Go-разработчика | Golang
@goproglib · 23,889
Telegram ranks this channel #75 of 91 here — alongside 90 others — read 17 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Fedkin is thinking” (@fedkin_thinking), 8,826 subscribers as measured 11 November 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.