Telegram RegisterThe public register of Telegram

Channel

Работая в айтишечке

@workinginit

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,469subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002330288041
TypeChannel
Username@workinginit
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/workinginit

Growth

1,4681,4691,468.56 August 2026 — 1,469 subscribers6 August 2026 — 1,469 subscribers6 August 2026 — 1,468 subscribers9 August 2026 — 1,469 subscribers6 August 20269 August 2026
4 measurements spanning 4 days. 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,468–1,469 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 23:311,469+1
6 Aug 2026, 21:021,468-1
6 Aug 2026, 07:461,469no change
6 Aug 2026, 03:511,469first reading

Engagement

15 posts held, back to 19 May 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
35.6%
avg views ÷ 1,469 subscribers
Avg views / post
523
3 posts measured
Reaction rate
3.06%
reactions ÷ views · ER floor
Posts in window
3
of 15 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 July 2026
Posts held15 (19 May 202624 July 2026)
Views total1,568
Reactions total48
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 07:46 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

23 Jul 2026, 07:55 UTC≈544 views14 reactionsread 6 August 2026
Photo

☕️ Loop Engineering: что за новый термин В последнее время все носятся с Loop Engineering как с писаной торбой. Особенно активно его стали обсуждать после фразы Бориса Черного, создателя Claude Code: он больше не пишет промпты — вместо этого пишет лупы, которые сами промптят Claude. Попробовал разобраться что это и как работает. Вышло вот что. Допустим, каждый понедельник вы собираете отчёт для команды. Нужно выгр

22 Jul 2026, 07:45 UTC≈523 views16 reactionsread 6 August 2026
Photo

☕️ CodexBar — лимиты AI-инструментов прямо в меню баре Антропики недавно меня забанили, пришлось перейти на Codex. Начал искать аналог Usage Tracking, и нашёл - называется CodexBar - показывает остатки лимитов и время до их сброса. И самое главное - не только Codex'а, можно настроить и для Claude и для Cursor и др. Что умеет: — Отслеживает лимиты сессии, недели и месяца — Поддерживает 60+ провайдеров: Codex, Claude

26 Jun 2026, 12:43 UTC≈855 views15 reactionsread 6 August 2026
Photo

☕️ От вайбкодинга к agentic engineering А вот и подтверждение к мыслям из предыдущего поста. Google опубликовали интересный whitepaper — «The New SDLC With Vibe Coding» про то, как меняется разработка, когда код пишет агент, а не человек. В доке ребята обсуждают вайбкодинг и agentic engineering — говорят, что это не две альтернативы, а два конца одного спектра. Разница между ними в том, насколько строго вы проверя

18 Jun 2026, 17:25 UTC≈1,130 views38 reactionsread 6 August 2026
Photo

☕️ Кем станет аналитик, когда ИИ научился писать SQL Сейчас модно рассуждать на тему того, как кого-то заменит ИИ. Решил посмотреть на роль аналитиков - так как они являются основными пользователями моих продуктов. Начнем с главного — заменят не аналитика — заменят кусок работы: накидать черновик запроса, собрать табличку, поймать аномалию глазами, нарисовать первый график. Это ИИ уже делает быстрее аналитиков. Но

5 Jun 2026, 16:41 UTC≈978 views14 reactionsread 6 August 2026
Photo

☕️ Агенты как пользователь Возникла мысль, что продакты должны теперь держать в голове ещё один сегмент пользователей — LLM-агентов. Ладно, не прям отдельный сегмент, скорее агент — это не персона, а режим потребления, вторая поверхность продукта для существующего пользователя. Идея простая: агенты уже сейчас лезут в наши интерфейсы. Кликают, заполняют формы, дёргают API, оформляют заказы. Делают это коряво и нена

29 May 2026, 12:23 UTC≈1,220 views14 reactionsread 6 August 2026
Photo

☕️ Четыре репозитория со скиллами для аналитики Покопался на гитхабе и отобрал четыре репозитория со скиллами под аналитику данных — те, что реально зашли. Мой фаворит — ai-analyst - это просто комбайн, делает всё 🔥 Напомню: скилл — это папка с инструкцией и шаблонами, которую Claude подгружает сам, когда видит подходящую задачу. Один раз кладёте в неё свои правила, метрики и схему — и дальше не объясняете контекст

27 May 2026, 14:13 UTC≈870 views12 reactionsread 6 August 2026
Photo

Не, ну ChatGPT/Codex конечно пушка! Надо было коллеге рассказать разницу - попросил поресерчить и сделать инфографику

27 May 2026, 07:16 UTC≈855 views14 reactionsread 6 August 2026
Photo

☕️ Команды будущего: несколько мыслей Да здравствует эра дженералистов. Всех специалистов упакуют в скиллы, а дженералисты будут этими скиллами хороводить Решил сесть осмыслить как AI меняет команды. Надеваю шапку футуролога. Поехали. 1️⃣ Команды станут меньше, но не так, как это любят подавать. Не «увольняем половину, AI справится». А иначе: исчезает не работа, а передача работы между людьми. Раньше она шла цепоч

Showing the 12 most recent of 15 posts we hold for @workinginit. 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 — 198,409 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

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.

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

“Работая в айтишечке” (@workinginit), 1,469 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/workinginit.

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.