Channel
@yl_code
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
18subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001686353738 |
|---|---|
| Type | Channel |
| Username | @yl_code |
| Description | Технологии, приёмы, кейсы – всякое из практики |
| Created | Between 1 December 2021 and 16 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/yl_code |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:01 | 18 | no change |
| 8 Aug 2026, 23:32 | 18 | first reading |
8 posts held, back to 16 January 2023 — 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 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 8 posts for this entry, the most recent from 22 February 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3 | 75.0% | |
| 👍 | 1 | 25.0% |
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 3 of the 8 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 16 January 2023 to 22 February 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Два любимых паттерна в Go, которые было бы здорово видеть в других языках: 1. Работа с ошибками через явную передачу: func isStuffGood() (bool, error) { res, err := helperThatCanFail() if err != nil { return false, err } res2 := helperThatNeverFails(res) return res2, nil } Снижает когнитивную нагрузку: всегда понятно, нужно ли что-то обрабатывать, никаких тебе "добавить try-catch или по…
👍1
Написал про некоторые ключевые различия TON от Solidity: https://www.linkedin.com/feed/update/urn:li:activity:7228317246828290048/
TDD на фронте – это довольно удобно. Вот хорошая иллюстрация (и это правда так работает): можно написать более-менее всю логику компоненты, вообще не глядя в браузер. Для стилей, конечно, придётся заглянуть – да и разок протестировать, чтобы обнаружить какие-то смешные баги типа React показывает 0 вместо ничего, но в целом такое разделение упрощает жизнь и ускоряет разработку (не говоря уже о рефакторинге, добавлени…
Немного об accessability в вебе глазами разработчика. Вы когда-нибудь пробовали понять, какую методологию использовать, чтобы сделать интерфейс доступным хотя бы для незрячих пользователей? Скорее всего, ваша попытка разбилась о чтение разного рода спецификаций "за всё хорошее" и крайне фрагментарые статьи, про которые у вас нет даже возможности понять, насколько дельные вещи там написаны. Некоторое время назад я пр…
Печатать много занимает время, особенно когда дело касается таких частых команд как git. Зато можно пользоваться алиасами: зайти в .gitconfig, добавить секцию [alias] и прописать туда что-то вроде: [alias] ch = checkout lo = log --oneline dc = diff --cached И тогда можно писать, например, git lo -n 3 вместо git log --oneline -n 3. Кстати, дока подсказывает, что задавать их тоже можно командой: git config --gl…
Не люблю много читать про новые технологии, но всё-таки иметь некоторый небольшой поток, чего можно почитать/чему поучиться, довольно полезно. В какой-то момент reviewing вопросов на Stackoverflow обеспечивал мне такой поток. Со временем, я решил, что не готов тратить время на reviewing; эато (не помню, раньше или позже) начал почитывать рассылки. Если в плане веба и немного вширь мне раз в неделю присылает письмо …
🔥1
в чатике FreeCodeCamp немного рассказал про использование ChatGPT для разработки, поделюсь-ка примером с eslint: штука показательная – искать (бывает) долго, спросить – минута. Приятно понижает порог входа во всякие "микротехнологии", типа разных шаблонизаторов, препроцессоров, CI/CD и прочего, где написать часто нужно немного, знать бы рецепт
🔥2
а вообще ChatGPT неплох как learning assistant. Вот, например, не совсем тривиальный вопрос по TypeScript. Увы, потребовалось 6 итераций, чтобы получить подходящий ответ на вопрос, но это, например, быстрее, чем задавать вопрос на SO и ждать; и, вероятно, быстрее, чем гуглить то, чего заранее не знаешь. TL;DR – первый и предпоследний скрин
Showing the 8 most recent of 8 posts we hold for @yl_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 — 928,584 of 1,160,990entries 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.
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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Яков разрабатывает” (@yl_code), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/yl_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.