Channel
@analytics_engineer_1337
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
630subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002812483950 |
|---|---|
| Type | Channel |
| Username | @analytics_engineer_1337 |
| Description | Заметки о хардах и софтах в мире больших данных. Широкий спектр затрагиваемых тем. Учебные материалы, размышления, мотивация. |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/analytics_engineer_1337 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:50 | 630 | no change |
| 7 Aug 2026, 17:27 | 630 | first reading |
19 posts held, back to 7 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 1 pageof 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 19 posts for this entry, the most recent from 20 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
273 reactions across 19 posts, in 10 distinct kinds. The most used accounts for 40.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 111 | 40.7% | |
| 🔥 | 68 | 24.9% | |
| 👍 | 64 | 23.4% | |
| 🤮 | 7 | 2.56% | |
| 👏 | 6 | 2.20% | |
| 🥰 | 6 | 2.20% | |
| 💩 | 5 | 1.83% | |
| 👎 | 4 | 1.47% | |
| ⚡ | 1 | 0.366% | |
| 🤩 | 1 | 0.366% |
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 19 of the 19 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 273reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 7 January 2026 to 20 April 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.
#DE #харды #база_знаний https://youtu.be/Wk_dXBdsoyc Я изначально хотел сделать материал по DAG-фабрике, но наткнувшись на это видео Корсакова, понял, что в целом он уже показал оптимальный и удобный вариант использования DAG-фабрик. Генерация похожих DAG'ов, но отличающихся, например, по расписанию, ограничениям по одновременным таскам или параметрам в самом коде. Считаю JSON и yaml конфигурации самым удобным сп…
👍4❤2🔥2👏1🤮1
#харды #DA #база_знаний Там Заскуль Питона выложил курс на степик по пандасу для новичков. Будет полезно начинающим аналитикам!
🔥10🤮3❤2👏2
Сделал свой первый курс по pandas. Курсов таких очень много, но гештальт определенный для себя закрыл. Смотрел на несколько курсов, которые есть в доступе, проблема в том, что там в формате: "Выбери правильный вариант ответа", а хотелось дропнуть полноценный. КУРС ДЛЯ НОВИЧКОВ 👦 Намучился с тестами и составлением заданий, а также с валидацией всего что есть. Ну ничего страшного, все заработало, по крайнем мере я та…
🔥9❤3👏2💩1
#харды #база_знаний #DE Наткнулся на крутой русскоязычный канал по Data Engineering на ютубе😎 https://www.youtube.com/@DataLikeQWERTY/videos Автор не только объясняет многие актуальные дата инженерные темы (как начать работать с s3 или modern data stack, нюансы Airflow, Docker, алгоритмы сжатия данных и т.д.), но и часто делает репозитории со своими полигончиками и на них показывает пайплайны данных и дата инструм…
👍8❤4👏1🤮1
#личное По поводу ситуации с блокировкой телеграма - я остаюсь, канал не брошу
👍8❤6🔥1🤮1
Video message, posted without a caption
❤8🔥1🥰1
#харды #база_знаний #DE #DA_PA Сегодня я впервые добавил книги в базу знаний🕺 Сразу для дата инженеров и продуктовых аналитиков! В принципе, дата инженерная книга может быть полезна и DWH аналитикам для общего развития. Книга “Основы инженерии данных”, Джо Риса и Мэтта Хоусли Фундаментальная базовая книга по инженерии данных. Полезна как вкатывающимся, так и уже вкатившимся, но развивающим кругозор дата инженера…
👍8❤4🤩1🤮1🥰1
Надо сегодня восьмамартовый пост про Хорошаву сделать
❤11🔥1🥰1
Поздравляю всех женщин с 8 марта и прикладываю фотографии кошки Хорошавы. Она мурчит и желает всем отличного праздника!😺
❤7🔥1🥰1
#харды #база_знаний #DA #DE Статья по макросам с jinja в DBT готова🐹 Я бы сказал, что макросы скорее аналитические получились, нежели дата инженерные, но по дата инженерным я еще пройдусь в отдельных материалах🎩 Макросы в DBT нужны, чтобы один раз описать кусок логики (SQL + Jinja) и переиспользовать его во многих моделях, тем самым уменьшая дублирование и упрощая масштабирование проекта. Динамическое создание та…
❤7👍2🔥1
https://youtu.be/5iTotKJua_E?is=GSGbptYMvzCujHCT Я тут в кино снялся. Главное, ребята, сердцем не скуфеть! Всем новоприбывшим привет, сейчас поедем! Кстати, жинжа макрос дбт гайд уже сегодня. И ещё: не то чтобы я умер в последний месяц, но зато насобирал контента для двх аналитиков в плане собеседований🎧
🔥7❤4👍4💩2
#база_знаний Я сжал длиннопосты в истории канала, снабдил ссылками на базу Появился раздел черновиков в базе знаний - там сырые материалы для будущего контента. Например, можно посмотреть композ код постгренка или увидеть вопросы с собесов. тык Однако сырость материалов означает их незавершенность и риски ошибок. Как-то так. (Но постгренка я точно уже запускал😁) Черновики далее афишироваться не будут, только зав…
❤6🔥4👍1🥰1
Showing the 12 most recent of 19 posts we hold for @analytics_engineer_1337. 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 — 1,070,830 of 1,176,251entries 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 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Аналитический Инженер” (@analytics_engineer_1337), 630 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/analytics_engineer_1337.
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.