Channel
@analytics_engineer
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,308subscribers
+3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001526549365 |
|---|---|
| Type | Channel |
| Username | @analytics_engineer |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/analytics_engineer |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 10:17 | 1,308 | +3 |
| 7 Aug 2026, 06:34 | 1,305 | no change |
| 6 Aug 2026, 09:05 | 1,305 | first reading |
20 posts held, back to 26 September 2025 — 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 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 28 July 2026 |
|---|---|
| Posts held | 20 (26 September 2025 – 28 July 2026) |
| Views total | 2,186 |
| Reactions total | 36 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 09:05 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.
Решил сделать площадку для обсуждений / созвонов по Agentic / AI Engineering in Data на основе топика в @de_zoomcamp. Если кому-то интересно, залетайте туда. Первой темой возьмем Data / Analytics Agents - как они работают, зачем нужны и как их строить. Тема обширная, поэтому пойдем top-down, обсудим все компоненты хай левел, а потом будем разбирать каждый из них в следующих созвонах. Базовые статьи (часть из них, д…
Ищу к себе двух инженеров, удаленка (100-150$k) Вакансия ближе к разработке и ML https://job-boards.eu.greenhouse.io/dwelly/jobs/4929545101 Вакансия ближе к разработке https://job-boards.eu.greenhouse.io/dwelly/jobs/4928198101 PS: чуть позже еще будет пара вакансий попроще. Можете писать мне, зареферю :) PS2: если хотите в Лондон - можем сделать визу
в бигтехе после сокращений, флатерингов, лейфоф промзошла тихая девальвация уровней. она и раньше была, но сейчас прям пик если вы мидлл, то ожидания от вас как от сеньор разработчика, отношение как к джуну. для роста нужно вести проект уровня стаффа если джуниор, то должны работать минимум на уровне миддла, для повышения нужно работать на уровне сеньора если сеньор, то пашите как стафф, тяните проект который пар…
DEMate - тот, кто тебя заменит Meta пошарила статью про DEmate - внутреннего AI-ассистента для data engineering, который не просто SQL / питон генератор кода, а готовый AI-слой для полноценного цикла разработки (ака накидаем md в контекст в первых версиях😂), учитывающим специфику внутренних систем Meta (а там без пол-литра иногда и не разобраться 🍺). Главный поинт в том, что LLM становятся полезными в enterprise-ин…
File, posted without a caption
Запись - https://www.youtube.com/watch?v=CE0K9ErBqsI Презентация в приложении. Вроде получилось довольно неплохо, хоть и с небольшими проседаниями, так как давно не делал презентаций на английском. Из интересного, удалось сделать полноценный pet project по генерации презентации чисто на промптах с добавлением валидаций на уровне text и image LLM-as-a-judge + multi-LLM asssessment. Любой новый промт включал полный ц…
Возвращаюсь в онлайн вебинары 🙂 Залечу на вебинар на следующей неделе во вторник в легендарный DataTalksClub к поговорить (угадайте про что 😘) про Agentic для дата инженеров. 📚Описание The Agentic Shift in Data Engineering: From Pipeline Builders to Architects of Controlled Chaos AI agents are changing data engineering on two fronts at once. In development, they compress the engineering loop: helping write SQL…
А ты все еще веришь в свой CLAUDE.md? Есть две категории вайбкодеров: - те, кто уже перешёл на pre-tool hooks - и те, кто ещё не положил прод, надеясь на md-файл 🙂 По последним новостям можно наблюдать уровень вариативности LLM.. или как быстро удалить все свои данные 👍 Но я конечно не такой, и все у меня в guardrails и обвязках (ага, конечно 😂) У меня в CLAUDE.md инструкция, что DROP TABLE возможен только при р…
Как там ДЕ в 2026? 👋 Ну раз все обсуждают, то ворвусь и я. 🫡 «I am so excited, what a time to live, data industry is changing a lot», - сказал мне дата директор моей орги, рассказывая, как он начал делать коммиты и пушить код в прод, вайбкодя презентации и отчеты в параллель. «I was excited a year ago, now I am anxious», - ответил я (как человек, закрывавший задачи кодогенерацией на 90% еще год назад). И пояснил,…
Агенты в дата-платформах 🤖 Я уже полгода вожусь с разными дата агентами и другими GenAI решениями для данных. Кодинг / контекст ассистенты уже поменяли индустрию кардинально, а с внутренними агентами ситуация еще интереснее 😘. Допустим, у вас в проде крутится дата агент-оркестратор. Он рулит десятком других агентов, те дёргают ещё по 10 тулов каждый. Сценарий успеха: автоматизировали дата-платформу на 95%, радикал…
Дружественная рекомендация по вакансии ML Data Engineer в Recraft - 90-130k £ base + options, London, visa support https://hrlunapark.notion.site/ML-Data-Engineer-2df39c37e87b809a8b74c348ff935797 Писать вопросы и кидать CV Феде из Luna Park - @owlkov Я уже рассказывал про свой собес в рекрафт https://t.me/analytics_engineer/78, а тут у ребят появилась еще более сочная позиция🍿 MLщики из рекрафта активны в лондо…
AI Safety триггеры 🤨 Словил нынче отказ Gemini и NanoBanana Pro генерить архитектурные диаграммы на данном промпте 😺 { "subject": "2D Data Flow: 'The Static Lookup'. \nTop: A 'Static Reference Table' (Blue, solid, labeled 'Users/Devices'). \nCenter: Fast-moving 'Event Stream' (Red data packets flowing right). \nBottom: Events passing through a 'JOIN' operator, emerging combined (Purple = Red + Blue). \nAnnotation…
Showing the 12 most recent of 20 posts we hold for @analytics_engineer. 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 — 607,710 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Nik в мире данных” (@analytics_engineer), 1,308 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/analytics_engineer.
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.