Короче, кажется, в предыдущих постах про наши с Тёмой Советы уже стало слишком легко потерять нить 😄 Поэтому мы сделали проще. Нам дали одну сложную задачу. Мы независимо прогнали её через два разных ИИ-Совета, а вместо ещё нескольких лонгридов собрали Арену, где решения можно сравнить напрямую. Как это работает: — сначала вы не знаете, где чей ответ;— проходите три коротких раунда: диагноз → риск → следующий ход…
![Telegram profile photo for [CPO] Feel your product / Tables](https://cdn.tgregister.com/av/f9/f9b3cdd81fe5f6bdcd0ed14b02a4e4d564a63a11070b2f9bccff630c18ac2957.jpg)
Channel
[CPO] Feel your product / Tables
@fyp_tables
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry
73subscribers
-1 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002574085640 |
|---|---|
| Type | Channel |
| Username | @fyp_tables |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/fyp_tables |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 18:21 | 73 | -1 |
| 18 Aug 2026, 07:03 | 74 | no change |
| 18 Aug 2026, 02:15 | 74 | first reading |
Engagement
15 posts held, back to 25 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 15 posts for this entry, the most recent from 16 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 31s
- Average length
- 1m 31s
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.
Reaction mix
115 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 34.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 40 | 34.8% | |
| custom 5386764531152198851 | 31 | 27.0% | |
| custom 5235794016926185566 | 27 | 23.5% | |
| 💔 | 6 | 5.22% | |
| 😁 | 5 | 4.35% | |
| 😱 | 5 | 4.35% | |
| custom 5235514221281687578 | 1 | 0.87% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 12 of the 15 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 115 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 25 July 2026 to 16 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.
Telegram Stars
- Stars received
- 1
- across the posts below
- Posts paid on
- 1
- of 15 we hold a reading for · 7%
- Most on one post
- 1
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fyp_tables. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 25 July 2026 to 16 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Пока Codex пишет мне фичу для заказа еды, решил посмотреть, кто вообще оплачивает этот банкет. Наткнулся на рилс. Хихик 🦦 «первоисточник»
😱5❤4custom 52355142212816875781
Рубрика: #субботний_контент 1) Даня, написал очень классную статью, про один из своих проектов. По моему чистый кайф. [читать] 2) История бренда Додо, а скорее — Фёдора Овчинникова. Мне было очень интересно посмотреть. [смотреть] А теперь CTA ❗️ Что думаете про Додо? Какой у вас был опыт взаимодействия с ними? Федя молодец? 😄 И второе: что интересного вам попалось за эту неделю? Что стоит посмотреть, послушать или …
custom 52357940169261855663❤1custom 53867645311521988511
Пятничное наблюдение, не рекомендация 😄 Мне недавно понадобилось поставить GPT и ещё пару приложений, которых нет в российском App Store. Менять регион, заводить отдельный аккаунт и разбираться во всей этой механике мне было лень. В итоге попробовал максимально простой путь: написал в чат поддержки своего банка и попросил помочь установить актуальное банковское приложение. Оказалось, что некоторые банки для этого…
custom 53867645311521988516❤2
Лучший ответ
- Мой50%
- Филиппа50%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
*я понимаю, что аудитория моего канала, и так все понимает, но на всякий случай, если ты поддерживаешь вариант из этого паблика, голосуйте за "Филиппа" 😘
😁3
Тёма, принимаю батл Советов 🤝 Коллеги вкинули нам непростое ТЗ: "Как масштабировать продажи и внедрения MWS Tables, если главная сила продукта — гибкость и возможность собрать почти любой процесс, но эта же гибкость делает каждую продажу и внедрение кастомными и плохо масштабируемыми? Где проходит баланс между платформой, готовыми коробками и услугой по настройке? Я отдал этот вопрос своему Совету мудрецов" Важная…
Тёма написал, что я у него спёр «Великий Совет». Не буду спорить. Спёр. А потом сделал то, что обычно делаю с чужими хорошими штуками: полез внутрь и начал всё переделывать. У Тёмы Совет собран вокруг функциональных ролей: продукт, бизнес, продажи, архитектура, маркетинг, финансы, риски. Приносишь гипотезу — нужные роли разбирают её, спорят и возвращают общий вердикт. Мне стало интересно: а что если важна не только…
custom 53867645311521988513❤2😁2
Недавно снова полез читать про культуру Netflix — и чем дальше, тем больше мне нравится не набор их отдельных практик, а то, как они собраны в одну систему. Там всё довольно жёстко и последовательно. Netflix исходит из идеи, что компания - это не семья, а скорее профессиональная спортивная команда. То есть задача не в том, чтобы любой ценой сохранить всех, кто когда-то оказался внутри. Задача - чтобы на каждой поз…
custom 52357940169261855667custom 53867645311521988515❤1💔1
Самые интересные цифровые продукты иногда заканчиваются чем-то очень физическим. Например - чашкой кофе. Сегодня на ИТ-пикнике у Tables была кофейня. И мне понравился один довольно простой момент: человек нажимает кнопку на экране - а через несколько минут другой реальный человек делает ему реальный кофе. Между этими двумя событиями успевает произойти довольно много. Сначала мы проверяем, выполнил ли гость задания …
❤8custom 53867645311521988513custom 52357940169261855662
Немного пятничного продуктового оффтопа. Я периодически играю в Path of Exile 2 и уже несколько лет наблюдаю за Grinding Gear Games. Ребята делают очень кайфовый продукт. Главный принцип, который я оттуда забираю: упрощать нужно вход, а не глубину. PoE не пытается прожить игру за тебя. Она даёт правила, а дальше — разбирайся, экспериментируй, собирай билд, иногда всё ломай и начинай заново. В общем, почти как CPO…
❤3custom 52357940169261855663custom 53867645311521988513
Есть одна вещь, к которой очень сложно привыкнуть, даже спустя много лет в продукте. Хорошие продукты тоже закрываются Сегодня увидел пост Льва о закрытии HomeBro. И почему-то стало немного грустно. Несколько лет назад, когда я ещё работал в Яндекс.Аренде, я случайно узнал о HomeBro — кажется, кто-то из пользователей рассказал мне про этот сервис. Помню, тогда мы даже обсуждали внутри команды, как было бы здорово …
❤6💔5
Showing the 12 most recent of 15 posts we hold for @fyp_tables. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Лучший ответ
- Мой50%
- Филиппа50%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 25 July 2026 to 16 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“[CPO] Feel your product / Tables” (@fyp_tables), 73 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/fyp_tables.
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.