24 Oct 2020, 21:49 UTC≈5,220 viewsread 6 August 2026
https://youtu.be/LgNXopcLb-g
Signed Vladimir 🦉 Kharaman
Channel
Frontend & Backend разработка
@frontend_and_backend
On this record: Growth · Engagement · Posts · Citations · Cite this entry
602subscribers
-3 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001052763425 |
|---|---|
| Type | Channel |
| Username | @frontend_and_backend |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/frontend_and_backend |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 06:21 | 602 | -2 |
| 13 Aug 2026, 18:17 | 604 | -1 |
| 6 Aug 2026, 17:47 | 605 | no change |
| 5 Aug 2026, 23:08 | 605 | first reading |
Engagement
20 posts held, back to 4 September 2018 — 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 20 posts for this entry, the most recent from 24 October 2020. An engagement rate over an empty window would be a number about nothing.
Recent posts
25 Jan 2019, 14:26 UTC≈11,200 viewsread 6 August 2026
Photo
Как вам такое? Proposal на Immutable data structures в #TypeScript Link: https://goo.gl/zgtHS1
Signed Andrew Danilenko
24 Jan 2019, 09:11 UTC≈9,880 viewsread 6 August 2026
Photo
Ребята из компании Verve, рассказывают почему они решили перейти на GraphQL и их дальнейший опыт. Link: https://goo.gl/rL9WKC
Signed Vladimir 🦉 Kharaman
22 Jan 2019, 15:49 UTC≈7,210 viewsread 6 August 2026
Photo
Worker threads в Node.js. Объяснение концепции и зачем это нужно. Link: https://goo.gl/oa9xV1
Signed Vladimir 🦉 Kharaman
21 Jan 2019, 12:00 UTC≈5,990 viewsread 6 August 2026
Photo
Советы о SSR в React приложениях. Link: https://goo.gl/qNjBR9
Signed Vladimir 🦉 Kharaman
15 Jan 2019, 01:21 UTC≈5,970 viewsread 6 August 2026
Photo
Небольшой туториал по выбору подходящей API парадигмы (#gRPC, #REST, #GraphQL) Link: https://goo.gl/syA3ww
Signed Andrew Danilenko
14 Jan 2019, 13:58 UTC≈5,120 viewsread 6 August 2026
Photo
Путешествие в микросервисную архитектуру. Цикл статей из 6-ти частей, где вы узнаете принципы работы микросервисов. Part 1: https://goo.gl/R3288D Part 2: https://goo.gl/7EuysN Part 3: https://goo.gl/cMa7rt Part 4: https://goo.gl/DnBMrn Part 5: https://goo.gl/CK8HcX Part 6: https://goo.gl/XxuNCH
Signed Vladimir 🦉 Kharaman
14 Jan 2019, 10:53 UTC≈4,440 viewsread 6 August 2026
Photo
Отличная статья с советами по тестированию node приложений. Однозначно подчерпнете что-то новое. Link: https://goo.gl/UokerW
Signed Vladimir 🦉 Kharaman
11 Jan 2019, 16:30 UTC≈4,300 viewsread 6 August 2026
Photo
Улучшаем производительность React приложений с помощью Lazy Loading и Suspense. Link: https://goo.gl/AG9bcb
Signed Vladimir 🦉 Kharaman
26 Nov 2018, 12:59 UTC≈4,480 viewsread 6 August 2026
Photo
Очень красивое представление того, как работает Vuex. Link: https://goo.gl/UmzajA
Signed Vladimir 🦉 Kharaman
20 Nov 2018, 12:21 UTC≈4,110 viewsread 6 August 2026
Photo
Worklets, Web Workers, Service Workers. Переходи по статье если не знаешь разницу Link: https://goo.gl/QHpVM9
Signed Vladimir 🦉 Kharaman
19 Nov 2018, 23:38 UTC≈3,630 viewsread 6 August 2026
Photo
Состояние JS 2018 с приятной визуализацией. Фреймворки на клиенте/бекенде, тестирование и многое другое Link: 2018.stateofjs.com
Signed Vladimir 🦉 Kharaman
Showing the 12 most recent of 20 posts we hold for @frontend_and_backend. 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.
Mentions
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Frontend & Backend разработка” (@frontend_and_backend), 602 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/frontend_and_backend.
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.