Posted without readable text
❤🔥8🔥6

Channel
@bankirudev
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
176subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003911692175 |
|---|---|
| Type | Channel |
| Username | @bankirudev |
| Created | Between 1 April 2026 and 1 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/bankirudev |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 55% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 23:18 | 176 | -1 |
| 29 Aug 2026, 18:44 | 177 | +3 |
| 21 Aug 2026, 23:26 | 174 | -3 |
| 8 Aug 2026, 13:32 | 177 | no change |
| 6 Aug 2026, 20:55 | 177 | +1 |
| 6 Aug 2026, 03:48 | 176 | first reading |
14 posts held, back to 1 July 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 page of 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 14 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
404 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 39.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 160 | 39.6% | |
| ❤🔥 | 61 | 15.1% | |
| ❤ | 55 | 13.6% | |
| 👍 | 46 | 11.4% | |
| 😁 | 20 | 4.95% | |
| 🌚 | 11 | 2.72% | |
| 👏 | 10 | 2.48% | |
| 👾 | 10 | 2.48% | |
| 💅 | 10 | 2.48% | |
| 🤷♂ | 9 | 2.23% | |
| 👨💻 | 6 | 1.49% | |
| 👻 | 3 | 0.743% | |
| 😐 | 3 | 0.743% |
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 14 of the 14 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 404 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 1 July 2026 to 5 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.
Posted without readable text
❤🔥8🔥6
Posted without readable text
❤14🔥8
Posted without readable text
❤🔥15🔥13👍12
Posted without readable text
🔥16👍12👏1
мем.пятница.актуалочка Меня зовут Женя, я деврел в Банки.ру и я все еще люблю мемы. Один супер-жизненный добавил в этот пост 😁 Делитесь своими мемами в комментариях!
😁19👾4
Posted without readable text
🔥18❤🔥10❤6
Posted without readable text
🌚11❤6👻3
Posted without readable text
🔥20❤6❤🔥5👍2
Одна карьерная история в Банки.ру Всем привет! Меня зовут Рита, я ведущий системный аналитик в Банки.ру. Ко мне пришел Женя (наш деврел), сказал, что я крутышка, и предложил рассказать про мой карьерный трек в Банки.ру. И вот мы тут. Поехали! Весь путь по грейдам и датам — на карточке выше, а тут расскажу подробности. Что было переломным проектом? Разделение команды, тогда появилось гораздо больше самостоятельност…
❤🔥22💅10👍7
ИИ для QA: как мы перестали тратить часы на подготовку Acceptance Criteria Всем привет! Я Марго, QA-инженер в Банки.ру. Раньше подготовка AC (Acceptance Criteria – чек-лист, по которому проверяем готовность задачи) была самой трудоемкой частью моей работы: перечитать Jira, поднять Confluence и макеты в Figma, вспомнить, что обсуждали на груминге. Мы это автоматизировали. Что получилось: Скилл на Claude Sonnet сам …
🔥15👍6❤4
мем.пятница.актуалочка Меня зовут Женя, я деврел в Банки.ру и я люблю мемы. Один на злобу дня добавил в этот пост. А на чьей стороне вы? 👨💻 — пишу сам: только классика, только хардкор! 🔥 — 50/50: иногда код, иногда вайбкод 👾 — не помню, когда писал код руками
🔥17👨💻6👾6
Что будет, если дать нейросети угадать баг Всем привет! Меня зовут Никита, я фронтенд-инженер в Банки.ру. Сегодня расскажу, как я прогнал реальные баги по CJM через нейросеть вслепую и сравнил ее гипотезы с настоящими git diff по закрытым задачам. Если коротко: даже без хитрых настроек нейросеть попадает в реальный фикс чаще, чем я ожидал. Детали в карточках. Через год ИИ будет сам закрывать простые баги? 🔥 — да,…
🔥14🤷♂9😐3
Showing the 12 most recent of 14 posts we hold for @bankirudev. 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.
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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“код.ии.прод” (@bankirudev), 176 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/bankirudev.
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.