5 Aug 2026, 21:51 UTC21 viewsread 10 August 2026
https://x.com/devmargooo/status/2084918449508073848?s=46&t=SfiwLAodNbDIA8F67QQIow
Channel
qa.log
@qa_cry
On this record: Growth · Engagement · Posts · Citations · Cite this entry
66subscribers
-2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001534496420 |
|---|---|
| Type | Channel |
| Username | @qa_cry |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/qa_cry |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 03:57 | 66 | -1 |
| 17 Aug 2026, 11:42 | 67 | -1 |
| 10 Aug 2026, 00:47 | 68 | no change |
| 9 Aug 2026, 16:33 | 68 | first reading |
Engagement
20 posts held, back to 26 May 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 137.4%
- avg views ÷ 66 subscribers
- Avg views / post
- 90.7
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (26 May 2026 – 5 August 2026) |
| Views total | 272 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 00:47 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.
Recent posts
4 Aug 2026, 11:50 UTC31 viewsread 10 August 2026
Photo
В подтверждение гипотезы о смене парадигмы работы с продуктом в эпоху агентной-инженерии вышел новый инструмент от JetBrains - Repository Intelligence - слой знаний над репозиторием. Основная мысль статьи - современные агенты уже умеют писать код. Их главный ограничитель - не генерация, а понимание проекта. Repository Intelligence - это попытка заменить бесконечное чтение файлов структурированным представлением зна…
29 Jul 2026, 11:51 UTC220 viewsread 10 August 2026
#vacancy #computervision #hardwareengineer Vision Hardware Engineer AI-based quality control system for a production line in Thailand. The system inspects soft plastic packaging on a conveyor belt and detects defects such as tears, dents, deformations, and damaged packaging in real time. Looking for an engineer with hands-on experience in: -industrial cameras (Basler, FLIR, Hikrobot, etc.) -lighting / optics / con…
28 Jul 2026, 11:45 UTC41 viewsread 10 August 2026
Поднимаем абстракцию еще выше Мы готовим инфраструктуру вокруг агента с версионированием - это разработка (context engineering) Затем продумываем пайпы, по которым будет происходить взаимодействие процессов между собой - это девопс (delivery engineering) И в конце собираем сценарии, проверяющие, что те или иные задачи по-прежнему решаются в пределах ожидаемого; поднимаем проекты, как тестовые данные - это тестиров…
21 Jul 2026, 13:03 UTC64 viewsread 10 August 2026
Оффтоп по откликам на вакансию Все заявки отправлены Ответы в отрицательных случаях не гарантируемы, но запрошены
21 Jul 2026, 11:15 UTC65 viewsread 10 August 2026
Стоит так же упомянуть, что высокая детализированность параметров оркестратора или частных агентских инструкций может казаться полезной только на первый взгляд. Однако при наличии строгих указаний о принципах работы агента исчезает основной смысл использования LLM-моделей - недетерминированность. То, что может казаться проблемой, с обратной стороны, является и преимуществом, поскольку в ином случае простор «мысли»…
16 Jul 2026, 11:25 UTC78 views0 reactionsread 10 August 2026
Photo
Собираем агента-оркестратора, подключаем к нему mcp-сервер и библиотеку со скиллам той или иной версии в качестве шаблона/каркаса одного из новых звеньев разработки. Отдаем задачу и получаем готовое решение, перенаправляя усилия на создание дата-сетов, сценариев и аналитики под тестирование версий теперь уже серверов и библиотек. И замыкаем более верхнеуровневый новый цикл работы над продуктом. Это больше не инжин…
14 Jul 2026, 11:22 UTC71 viewsread 10 August 2026
Photo
Классический релиз держится на негласном допущении: поведение системы живёт в коде сервиса. Поэтому мы версионируем код - теги, чарты, образы. С появлением агентов работа над проверкой работоспособности версий сервисов становится не просто недоутилизированной, но и архаичной. Кроме того, из-за новизны тренда и отсутствия систематизации наблюдается увеличение числа самописных вариантов инстуркций для агентов и сабаге…
9 Jul 2026, 09:52 UTC209 viewsread 10 August 2026
Вакансия #aqa #autoqa #стажировка Отклик - в директ канала
25 Jun 2026, 12:56 UTC194 views0 reactionsread 10 August 2026
Не одним конфигурационным файлом для использования AI-агентов единым - попробуем создать свой подключаемый mcp-сервер на примере опенсорсного продукта rocket.chat вкупе с соответсвующим файлом-инструкцией AGENTS.md rocket.chat - мессенджер, первый неструктурированный слой, в котором можно получить сообщение/тред с “проблемой”, ссылками на требования и прогоны тестов с ошибками. И не вникать в содержимое многочисленн…
11 Jun 2026, 11:14 UTC146 viewsread 10 August 2026
Что касается второй части работы с opencode - AGENTS.md: существует огромное множество предзаполненных шаблонов инструкций для агентов в сети. Можно использовать такой вариант wlasadd/claude-autotest-skills, а можно самостоятельно попросить подключенного агента изучить проект и сагрегировать некий набор шаблонов и практик, уже принятых за образец, и двигаться далее в том же стиле.
10 Jun 2026, 11:03 UTC110 viewsread 10 August 2026
Блок 6. opencode.json - agent (plan / build / reviewer) Переписывает под-агентов - три профиля поведения с разными правами и промптами. plan - безопасный анализ: "plan": { "model": "", "description": "Безопасный агент для анализа, планирования и объяснения кода без изменения файлов и запуска команд", "temperature": 0.1, // почти детерминированный, минимум «фантазии» "steps": 30, // максимум…
Showing the 12 most recent of 20 posts we hold for @qa_cry. 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 — 655,834 of 1,621,754entries 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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“qa.log” (@qa_cry), 66 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/qa_cry.
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.