Telegram RegisterThe public register of Telegram

Channel

<ассоциативный максим/> - React, Angular, Node.js, NestJS, JavaScript, TypeScript, Vue, Frontend

@am_code

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

80subscribers

+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-1001276022100
TypeChannel
Username@am_code
DescriptionПро разработку. В основном на #JavaScript #TypeScript (#angular, #react, #vuejs, #nodejs, #nestjs, #qwik, #bun, #frontend) p.s. совсем не Максим, это просто игра слов. Типа, ассоциативный массив, поняли, да? Чат - @am_code_chat
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/am_code

Growth

807 August 2026 — 80 subscribers9 August 2026 — 80 subscribers7 August 20269 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 79–81 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 19:1580no change
7 Aug 2026, 01:1780first reading

Engagement

20 posts held, back to 20 December 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 11 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
52
Videos
4
Links
119

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

Measured directly from 1 video 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.

Recent posts

11 Mar 2026, 09:38 UTC140 viewsread 9 August 2026

Сравнение производительности svg в зависимости от способа их встраивания ➡️ https://joanleon.dev/en/svg-optimization/ 👍Подписаться | 🔥Бустануть

18 Feb 2026, 16:44 UTC173 viewsread 9 August 2026

Набор снипетов «как решить старые проблемы современным css» ➡️ https://modern-css.com 👍Подписаться | 🔥Бустануть | #am_cheatsheet

14 Feb 2026, 18:44 UTC153 viewsread 9 August 2026

Ещё один рейтинг LLMок (теперь от OpenRouter’a) ➡️ https://openrouter.ai/rankings 👍Подписаться | 🔥Бустануть | #am_cheatsheet

7 Feb 2026, 17:16 UTC164 viewsread 9 August 2026

Рейтинг LLMок под разные типы задач ➡️ https://arena.ai/leaderboard/ 👍Подписаться | 🔥Бустануть | #am_cheatsheet

1 May 2024, 10:15 UTC≈1,160 viewsread 9 August 2026
Photo

The Front End Developer/Engineer Handbook 2024 Структурированный список полезных знаний со ссылками и инструментами для фронтендеров ➡️https://frontendmasters.com/guides/front-end-handbook/2024/ 👍Подписаться | 🔥Бустануть | #am_cheatsheet

24 Apr 2024, 15:24 UTC631 viewsread 9 August 2026
Photo

TypeScript Tip Вы можете использовать "as const" на template literal string, чтобы заставить TypeScript вывести эту строку. Без "as const" по умолчанию будет выводиться "string". 👍Подписаться | 🔥Бустануть | #am_tips

5 Apr 2024, 12:18 UTC557 viewsread 9 August 2026
Video

OCR тула (распознавание текста) работающая на клиенте ➡️https://tools.simonwillison.net/ocr Сорсы - https://github.com/simonw/tools Статья - https://simonwillison.net/2024/Mar/30/ocr-pdfs-images/ 👍Подписаться | 🔥Бустануть | #am_tools

28 Mar 2024, 11:34 UTC501 viewsread 9 August 2026

Сравнительная таблица JavaScript рантаймов (Node.js, Deno, Bun, etc.) ➡️ runtime-compat.unjs.io 👍Подписаться | 🔥Бустануть

26 Mar 2024, 15:12 UTC444 viewsread 9 August 2026

google-indexing-script - скрипт, который поможет ускорить индексацию вашего сайта гуглом https://github.com/goenning/google-indexing-script 👍Подписаться | 🔥Бустануть | #am_tools

22 Mar 2024, 14:08 UTC423 viewsread 9 August 2026
Photo

Сервис для сравнения клауд провайдеров https://getdeploying.com/ 👍Подписаться | 🔥Бустануть | #am_tools

19 Mar 2024, 15:01 UTC356 viewsread 9 August 2026

Избавляемся от неиспользуемого кода в TypeScript проектах https://camchenry.com/blog/deleting-dead-code-in-typescript

13 Mar 2024, 12:18 UTC368 viewsread 9 August 2026
Video

Million Lint - это своего рода ESLint для перфоманса: находит медленные участки кода и предлагает фиксы https://million.dev/blog/lint #am_tools

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

Citation-graph rank

Citation-graph rank — 370,855 of 1,345,403entries 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 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“<ассоциативный максим/> - React, Angular, Node.js, NestJS, JavaScript, TypeScript, Vue, Frontend” (@am_code), 80 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/am_code.

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.