Channel
@veged_and_code
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
1,589subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001697293637 |
|---|---|
| Type | Channel |
| Username | @veged_and_code |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/veged_and_code |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:36 | 1,589 | -3 |
| 10 Aug 2026, 00:58 | 1,592 | +3 |
| 7 Aug 2026, 02:14 | 1,589 | -2 |
| 6 Aug 2026, 07:32 | 1,591 | no change |
| 6 Aug 2026, 02:47 | 1,591 | first reading |
20 posts held, back to 22 January 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 2 pagesof 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 26 June 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.
205 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 42.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 42.0% | |
| 👍 | 49 | 23.9% | |
| 🔥 | 47 | 22.9% | |
| 👏 | 5 | 2.44% | |
| 🥱 | 4 | 1.95% | |
| 👎 | 3 | 1.46% | |
| 🤡 | 3 | 1.46% | |
| ⚡ | 2 | 0.976% | |
| 🥰 | 2 | 0.976% | |
| 💩 | 1 | 0.488% | |
| 🤗 | 1 | 0.488% | |
| 🤪 | 1 | 0.488% | |
| 🤮 | 1 | 0.488% |
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 15 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 205reactions 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 22 January 2026 to 26 June 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @veged_and_code. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 22 January 2026 to 26 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Вчера провели YoungCon 2026 и финал баттла вузов. В этом году экспериментально добавили в формат соревнование с использованием участниками ИИ на базе нашего SourceCraft.dev (кстати, внутри него появился Вайбкрафт). А чтобы ещё поддержать изучение новых технологий я, как автор модулей Практикума про использование ИИ в программировании, выпросил эксклюзивную скидку 25% для всех, кто читает меня!
❤4🔥3🤡3👍2💩1🤪1🤮1
Второй подкаст, который мы записали с Вовой в Новосибирске в перерывах между CodeFest:
#ГриненкоПро №10 про найм и образование с приходом ИИ В гостях снова Сергей Бережной — CTO Практикума и директор по взаимодействию с разработчиками в Яндексе. Но на этот раз говорим о том, что происходит с наймом в IT после появления нейронок, как быть джунам, можно ли честно проходить собеседование с AI, почему успешный GitHub-проект не заменяет интервью и чему теперь учиться, если новые модели выходят каждую недел…
❤3
На полях CodeFest записали с Вовой целых два выпуска его подкаста! Вот первый:
Подкаст #ГриненкоПро №7 про изменения в управлении командами разработки с приходом ИИ В этом выпуске говорим с Сергеем Бережным — директором по взаимодействию с разработчиками и CTO Яндекс Практикума — о том, как меняется роль руководителя инженерными командами. https://www.youtube.com/watch?v=tP0pLd2ug1A Обсуждаем, почему LLM — это не «джун», но и не «сеньор», как меняется цена ошибки, почему без инфраструктуры, …
Продолжаем поддерживать опенсорс — раздали ежегодные гранты!
❤6👍3🔥2
Новый выпуск «Как ты кодишь?» с Вовой Гриненко! Возможно рубрику уже надо переименовывать в «Как ты вайбкодишь?» или даже «Как ты дипкодишь?»
🔥6❤4👍2
В этом году Летние Школы снова будут в старинном оффлайн формате! … Ещё можно успеть присоединиться самим и/или позвать знакомых!
🔥6👎1
🐣 Приём заявок в Летние школы Яндекса — до 3 мая, пора! Есть чуть больше двух недель, чтобы подать заявку и пройти тестовое задание. И ещё несколько причин зарегистрироваться: 1. Быстрый путь к оферу Познакомишься с разными сервисами и выберешь, где хочешь начать карьеру. У выпускников — сокращённый отбор на стажировку 2. Бесплатное обучение Проезд и проживание в Айтиобщаге — тоже, если ты из другого города 3. Ма…
🔥3❤2👎2🥰2
Говорить мало. Экономить токен. Сегодня в рубрике #ЭкономимТокены хочу поговорить про завирусившийся скилл caveman. Он заставляет модель отвечать как пещерный человек: без вводных конструкций и прочей воды, сохраняя техническую суть. По бенчмаркам самого проекта экономия на выходных токенах составляет 22–87% в зависимости от типа запроса (важно: это именно ответы модели, не входящий контекст). Из примера в README:…
👍18❤9
«то пусто, то густо…» 😅 ещё один свежий подкаст!
Podlodka #470 – Vim Многие думают, что Vim давно уже не актуален и остался мемом и игрушкой для гиков. В выпуске мы обсудили, зачем можно его использовать в современном мире, когда вокруг куча IDE и текстовых редакторов, что из себя представляет осовремененная версия под именем NeoVim и почему она до сих пор актуальна и остается для многих разработчиков способом собрать персональную среду разработки под свой реальны…
🔥12❤3👍2
Showing the 12 most recent of 20 posts we hold for @veged_and_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 — 37,480 of 1,151,006entries 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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Veged and Code” (@veged_and_code), 1,589 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/veged_and_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.