Завтра https://gm.nexttick.it/go/data-structures-code-review
❤3🔥2👍1

Channel
@metarhia
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,691subscribers
-27 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001149467718 |
|---|---|
| Type | Channel |
| Username | @metarhia |
| Created | 24 May 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/metarhia |
Technology — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 22:21 | 3,691 | -5 |
| 14 Sept 2026, 04:15 | 3,696 | -8 |
| 6 Sept 2026, 07:58 | 3,704 | +2 |
| 30 Aug 2026, 12:49 | 3,702 | -5 |
| 27 Aug 2026, 15:43 | 3,707 | -4 |
| 25 Aug 2026, 02:25 | 3,711 | -3 |
| 21 Aug 2026, 18:39 | 3,714 | -2 |
| 18 Aug 2026, 10:56 | 3,716 | +2 |
| 15 Aug 2026, 18:48 | 3,714 | -1 |
| 12 Aug 2026, 18:23 | 3,715 | +1 |
| 9 Aug 2026, 08:51 | 3,714 | -4 |
| 6 Aug 2026, 04:32 | 3,718 | no change |
| 6 Aug 2026, 03:33 | 3,718 | first reading |
21 posts held, back to 9 July 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 4 pages 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
331 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 28.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 93 | 28.1% | |
| 👍 | 91 | 27.5% | |
| 🔥 | 59 | 17.8% | |
| 🤣 | 49 | 14.8% | |
| 💯 | 15 | 4.53% | |
| 😁 | 7 | 2.11% | |
| 🤩 | 4 | 1.21% | |
| 🤝 | 3 | 0.906% | |
| 🤯 | 3 | 0.906% | |
| ⚡ | 2 | 0.604% | |
| 👨💻 | 2 | 0.604% | |
| 🫡 | 2 | 0.604% | |
| 👎 | 1 | 0.302% |
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 20 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 344 reactions 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 9 July 2026 to 7 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.
Завтра https://gm.nexttick.it/go/data-structures-code-review
❤3🔥2👍1
На першій частині стріму про структури даних я обіцяв матеріали, а зрештою підготував ще й перші скіли для структур. Вони допомагають обирати вбудовані структури JavaScript, проєктувати власні та використовувати готові реалізації з metautil замість створення чергового велосипеда. На першій частині стріму про структури даних я обіцяв матеріали, а зрештою підготував ще й перші AI-скіли. 1. Вбудовані структури JavaScr…
❤3👍2🔥1
Світ був би набагато кращим, якби люди та роботи робили кілька простих речей - проміжні змінні замість складних виразів - давали б їм семантично корисні імена - і називали змінні в JavaScript ідентифікаторами
🤣11💯3❤1🔥1🫡1
Под стримом по структурам данных задали вопрос, какие AI модели я использую и какой харнес. Отвечаю развернуто, но вы должны понимать, это моя специфика разработки Я стараюсь по неделе переключаться между моделями, чтобы знать их состояние и чувствовать особенности, но для моих задач сейчас лучше всего подходит Sonnet 4.6 (даже не 5), Codex 5.3, Grok 4.5, они не очень умные, но мне не нужно, чтобы они были умные, з…
❤8👍6🔥6
Photo, posted without a caption
🤣17👍4💯3😁2🔥1
Стало сложно писать лучше чем Fable, я неделю оптимизировал под V8 три несчастные структуры данных, чтобы обогнать его: Unrolled List, Doubly List, Circular Buffer. Но не бойтесь, я завтра буду рассказывать не про то, как они устроены (картинка с 6 структурами), а как их использовать (картинка с 12 интерфейсами): https://youtube.com/live/qNAjrZ07un0
🔥15❤2😁2👍1👨💻1
Хочете зроблю скіли для генерації правдоподібного, навіть красивого говнокоду, щоб створити більше робочих місць?
👍36🤣16🤩4💯2👨💻1🤯1😁1
Курс Ильи Климова «Тестирование в эпоху агентов» AI уже умеет писать много кода, но без тестов, контрактов и автоматической проверки качества он завалит вас кодом и вы его даже не вычитаете, не говоря уже о том, что на глаз многие вещи просто не ловятся, особенно в таких объемах кода. Курс учит, как построить управляемую инфраструктуру, чтоб тестирование помогало дресировать AI. Особенно полезно тем, кто уже использ…
🤣5❤3⚡2👍1🔥1
Чому у JavaScript світі немає культури використання структур даних? Їх неправильно вчать, точніше, правильно, але цього замало, такі знання корисні тільки на завданнях з літкода і на співбесідах, а ось на практиці люди відразу забувають про структури даних і реальний код тільки: [], {}, Set, Map Я пошукав, як їх зазвичай викладають: - як влаштовані всередині та як працюють - як оптимізувати: CPU, memory - як оцінити…
🔥20❤5👍4🤝2
В NextTick мы регулярно проводим голосовые разборы для участников с платной подпиской. Один из последних стримов мы решили ненадолго открыть в Telegram-канале IT-Гильдии. AI уже умеет ускорять разработку. Проблема в том, что бизнесу не нужен код быстрее. Ему нужны решенные задачи. Это часовой разговор о том, что агентская эпоха уже меняет в работе разработчика: почему количество сгенерированного кода ничего не гово…
❤2👍2🔥2👎1🫡1
Posted without readable text
А тут альтернативний варіант входу без пароля: - Зберігання ключів у OPFS (у браузері) - Для генерації Web Crypto (ECDSA P-256) - Без використання Web Authn, Passkey https://github.com/HowProgrammingWorks/ChallengeSignIn
❤4👍3🔥2
Showing the 12 most recent of 21 posts we hold for @metarhia. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Node.js Ukraine Community” (@metarhia), 3,691 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/metarhia.
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.