Telegram RegisterThe public register of Telegram

Channel

Департамент Разработки

@DevQ_A

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,404subscribers

-14 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002493286662
TypeChannel
Username@DevQ_A
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/DevQ_A

Growth

1,4041,4181,4117 August 2026 — 1,418 subscribers7 August 2026 — 1,418 subscribers10 August 2026 — 1,413 subscribers13 August 2026 — 1,404 subscribers7 August 202613 August 2026
4 measurements spanning 7 days, net -14. 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 1,402–1,420 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 18:071,404-9
10 Aug 2026, 14:031,413-5
7 Aug 2026, 05:421,418no change
7 Aug 2026, 03:151,418first reading

Engagement

20 posts held, back to 28 July 2026the 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.

ERR · 30 days
2.82%
avg views ÷ 1,404 subscribers
Avg views / post
39.5
20 posts measured
Reaction rate
10.2%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (28 July 20266 August 2026)
Views total791
Reactions total73
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:15 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

73 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 21.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1621.9%
🙏1317.8%
😁1115.1%
🔥912.3%
👍56.85%
🤝45.48%
🆒22.74%
🎉22.74%
👀22.74%
👨‍💻22.74%
11.37%
🏆11.37%
👏11.37%
💩11.37%
🤣11.37%
🤯11.37%
🥴11.37%

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 18 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 73reactions 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 28 July 2026 to 6 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.

Recent posts

6 Aug 2026, 12:22 UTC33 views3 reactionsread 7 August 2026
Photo

«Самый ленивый senior» набрал почти 100k звёзд и сам поправил свой бенчмарк Ponytail — это не код, а набор инструкций для агентов. Философия простая: «пиши как самый ленивый сеньор, который видел все переусложнения». YAGNI в чистом виде. Сначала автор заявлял 80–94% меньше кода. Потом один контрибьютор ткнул в кривой baseline. Автор не стал отмазываться — пересобрал бенчмарк на реальных agentic-прогонах и честно оп

🏆1🔥1😁1

6 Aug 2026, 08:20 UTC30 views1 reactionsread 7 August 2026
Photo

Cloudflare открыл исходники своей внутренней «операционки» для AI-агентов Cloudflare выложил Cloudflare OS — то, чем их сотрудники реально пользуются каждый день. Это не просто чат с LLM. Это полноценный workspace, где агент знает контекст компании, навыки, которые вы ему дали, и может безопасно ходить по внутренним системам. Агент пишет и запускает код в изолированной среде, строит документы на живых данных, созда

🙏1

6 Aug 2026, 07:20 UTC31 views6 reactionsread 7 August 2026
Photo

⚠️ npm-червь добрался до зависимостей, которые многие даже не устанавливали напрямую 4 августа исследователи обнаружили вредоносный [email protected]. За несколько часов атака распространилась на пакеты из пространств Keyv и Cacheable, а затем начала заражать проекты других разработчиков. Опасность в том, что Keyv часто приезжает транзитивно: например, по цепочке eslint → file-entry-cache → flat-cache → keyv. Вредоносный

😁21🤯1🥴1🙏1

5 Aug 2026, 06:51 UTC31 views3 reactionsread 7 August 2026
Photo

Роб Пайк сформулировал пять правил программирования. Шестое гласит: правила №6 нет. Эти правила написаны почти 40 лет назад (ещё в конце 80-х), но звучат так, будто их придумали вчера специально для эпохи AI-агентов и «ваibe-coding». Кратко: Ты никогда заранее не угадаешь, где программа будет тормозить. Узкие места всегда в неожиданных местах. Измеряй. Не оптимизируй, пока не померил. И даже после измерения — тол

👍1🔥1🤣1

4 Aug 2026, 12:23 UTC33 views7 reactionsread 7 August 2026
Photo

HashiCorp выпустила public beta Vault Kubernetes Key Management. Теперь API-сервер Kubernetes может делегировать envelope encryption в Vault Enterprise. Ключи, которые защищают etcd, живут вне кластера — в управляемом trust domain Vault. Никаких изменений в application-коде. Особенно полезно для regulated-сред, multi-cluster и zero-trust. Пока только Enterprise и нужен доступ к EncryptionConfig, но для тех, кто уже

🎉2👍2🤝21

4 Aug 2026, 09:34 UTC33 views6 reactionsread 7 August 2026
Photo

TypeScript 7.0 с нативным Go-компилятором (10x быстрее) Microsoft официально выпустила TypeScript 7.0 — компилятор полностью переписан на Go. Билды ускоряются в 8–12 раз. VS Code codebase: было 125 секунд → стало 10.6. Память тоже заметно меньше. Логика type-checking осталась идентичной TS 6, просто теперь это нативный бинарник с параллелизмом. Стабильный programmatic API обещают в 7.1, но уже сейчас можно ставить n

21👍1😁1🙏1

4 Aug 2026, 06:33 UTC36 viewsread 7 August 2026
Photo

GitHub наконец-то нативно сделал Stacked Pull Requests (public preview) GitHub официально выкатил Stacked PRs в public preview. Теперь большие фичи можно дробить на аккуратные слои: каждый PR зависит от предыдущего, ревьюить можно параллельно, а мёрджить весь стек одним кликом (или по частям). Больше никаких гигантских PR на 2000+ строк и ручного ребейза веток. Особенно кайфово с AI-агентами — они генерируют тонны

3 Aug 2026, 06:29 UTC35 views3 reactionsread 7 August 2026
Photo

Дайджест июля 2026 от "Департамента разработки" Июль получился насыщенным: волна новых frontier-моделей, жёсткие меры против supply-chain атак, продолжающиеся сокращения в Big Tech на фоне рекордных AI-инвестиций и первые реальные кейсы, где агенты уже пишут и оптимизируют научный код. Вот самое важное. AI и модели OpenAI выпустила семейство GPT-5.6 (Sol — флагман, Terra — баланс цена/качество, Luna — быстрая и де

1😁1🙏1

1 Aug 2026, 13:19 UTC48 views2 reactionsread 7 August 2026
Photo

Новая сверхредкая роль 2026: Forward-Deployed Engineer. Их всего ~2000, а спрос вырастет на 2100% Пока всех сокращают, появилась роль, за которой уже охота. Forward-Deployed Engineer (FDE) — инженер, который встраивается в компанию-клиента и реально внедряет AI в продакшн так, чтобы был ROI. Исследование Christian & Timbers (июль 2026): Всего в США таких элитных специалистов ~2000. Спрос к концу года должен вырасти

1🙏1

1 Aug 2026, 12:18 UTC41 viewsread 7 August 2026
Photo

Парадокс 2026: AI-бум рекордный, а в tech уже 140 000+ увольнений Financial Times подсчитал: с начала 2026 года американские tech-компании сократили почти 140 тысяч человек. Amazon + Oracle + Meta + Microsoft — почти 50 тысяч из них. При этом компании одновременно заливают сотни миллиардов в AI-инфраструктуру. Monday.com на прошлой неделе объявила о сокращении ~20% штата (~630 человек) и прямо связала это с «AI-dri

1 Aug 2026, 08:09 UTC43 views5 reactionsread 7 August 2026
Photo

OpenAI: как AI-агенты уже ускоряют научный софт (геномика и не только) OpenAI выпустила field report по восьми реальным проектам, где учёные использовали Codex (и иногда Claude Code) для модернизации научного ПО. В основном genomics. Примеры: переписали legacy build-систему cyvcf2, ускорили симулятор HI.SIM на 31%, оптимизировали Hifiasm. Агенты сами ставили бенчмарки, предлагали кандидатов и делали рефакторинг, ко

2🤝2🔥1

31 Jul 2026, 12:07 UTC48 views4 reactionsread 7 August 2026
Photo

GitHub Actions теперь держит подозрительные workflow на ручном апруве Новая защита от supply-chain атак: если система считает workflow потенциально вредоносным (часто после компрометации credentials), run ставится на паузу. Запускается только после явного апрува collaborator’а с write-доступом через аутентифицированную веб-сессию. Работает автоматически на публичных репозиториях github.com. Никакой конфигурации не

🙏21😁1

Showing the 12 most recent of 20 posts we hold for @DevQ_A. 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 — 411,476 of 1,340,412entries 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 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.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Департамент Разработки” (@DevQ_A), 1,404 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DevQ_A.

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.