Telegram RegisterThe public register of Telegram

Channel

Пятничный кодер

@fridaycoder

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

37subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001708457333
TypeChannel
Username@fridaycoder
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/fridaycoder

Growth

377 August 2026 — 37 subscribers10 August 2026 — 37 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 36–38 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:4637no change
7 Aug 2026, 11:3537first reading

Engagement

20 posts held, back to 7 November 2023the 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 20 posts for this entry, the most recent from 13 February 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Videos
2
Links
34

Lifetime counters from Telegram’s own channel header, read 10 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 15s
Average length
38s

Measured directly from 2 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

64 reactions across 14 posts, in 12 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4875.0%
🔥34.69%
23.13%
👻23.13%
🤯23.13%
👀11.56%
💩11.56%
🗿11.56%
😡11.56%
🤓11.56%
🤝11.56%
🤣11.56%

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

Measured over the 20 most recent posts we hold, published 7 November 2023 to 13 February 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

13 Feb 2024, 08:38 UTC424 views8 reactionsread 10 August 2026

diffing algorithm React не просто перерендеривает полностью все дерево компонентов, он находит кусочки поддерева и обновляет их. Этот процесс называется diffing 1. Два элемента разных типов приведут к созданию разных деревьев. В контексте React, когда алгоритм сравнения ("diffing algorithm") обнаруживает, что два элемента имеют разные типы, он предполагает, что структура их дочерних элементов также будет отлича

👍61👀1

6 Jan 2024, 12:46 UTC290 views6 reactionsread 10 August 2026

Хоть сегодня и не пятница, покодим сегодня ? 18:30 по Москве

👍5🤓1

18 Dec 2023, 13:29 UTC372 views5 reactionsread 10 August 2026
Photo

Установил такую вот шутку, удобно когда стол маленький (120см) много пространства освобождается Делитесь вашим сетапом, интересно глянуть

🔥3👍2

6 Dec 2023, 08:11 UTC341 views6 reactionsread 10 August 2026

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

👍51

5 Dec 2023, 08:19 UTC256 views4 reactionsread 10 August 2026

Когда хук вызывается в нашем компоненте он создает очередь, где хуки представлены в виде связанного списка в порядке их вызова с каждым полем next хука указывающим на следующий хук. Поскольку они копируются из каждого рендера, мы видим, почему мы не можем вызывать хуки в условиях или изменять их порядок вызова от рендера к рендеру. baseState и baseUpdate соответствуют хука useState и useDispatch. useEffect самое гла

👍4

30 Nov 2023, 04:59 UTC313 views1 reactionsread 10 August 2026

https://youtu.be/yaDRgP8XQUw?si=73nWXKO_w39sNFtx

👍1

21 Nov 2023, 17:55 UTC216 viewsread 10 August 2026
Photo

Если я правильно понял, React испоьлзует MessageChannel для остановки выполнения работы и продолжения или другим словами ConcarentMode

19 Nov 2023, 19:59 UTC344 views3 reactionsread 10 August 2026

Ресурсы для обучения. Много идей для проектов. Особенно понравился codecrafters, где, например, для обучения docker предлагается написать собственный doker и так с каждой технологией/языком - https://github.com/practical-tutorials/project-based-learning - codecrafters.io - devchallenges.io - github.com/codecrafters-i… - bfe.dev - https://projectbook.code.brettchalupa.com/

👍3

17 Nov 2023, 12:59 UTC233 views1 reactionsread 10 August 2026

Сам не читал, но говорят интересно) https://habr.com/ru/companies/productivity_inside/articles/322980/

💩1

17 Nov 2023, 07:14 UTC194 viewsread 10 August 2026
Photo

Создатель JSON, Дуглас Крокфорд, создал новый язык программирования - Misty Какой-то Python и Yml

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

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.

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

“Пятничный кодер” (@fridaycoder), 37 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/fridaycoder.

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.