Telegram RegisterThe public register of Telegram
Telegram profile photo for Грокаем C++

Channel

Грокаем C++

@grokaemcpp

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Telegram's recommendations · Cite this entry

9,353subscribers

+37 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001849984659
TypeChannel
Username@grokaemcpp
DescriptionДва сеньора C++ - Владимир и Денис - отныне ваши гиды в этом дремучем мире плюсов. По всем вопросам (+ реклама) @ninjatelegramm Менеджер: @Spiral_Yuri Реклама: https://telega.in/c/grokaemcpp Мы на TGstat: https://tgstat.ru/channel/@grokaemcpp/stat
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/grokaemcpp

Topic

Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 the other topics.

Growth

9,3119,3679,3397 August 2026 — 9,316 subscribers7 August 2026 — 9,316 subscribers8 August 2026 — 9,313 subscribers11 August 2026 — 9,311 subscribers15 August 2026 — 9,327 subscribers18 August 2026 — 9,326 subscribers20 August 2026 — 9,323 subscribers27 August 2026 — 9,343 subscribers30 August 2026 — 9,348 subscribers2 September 2026 — 9,349 subscribers6 September 2026 — 9,355 subscribers10 September 2026 — 9,367 subscribers14 September 2026 — 9,363 subscribers18 September 2026 — 9,362 subscribers28 September 2026 — 9,363 subscribers5 October 2026 — 9,362 subscribers12 October 2026 — 9,353 subscribers15 October 2026 — 9,351 subscribers19 October 2026 — 9,342 subscribers22 October 2026 — 9,354 subscribers25 October 2026 — 9,350 subscribers31 October 2026 — 9,347 subscribers3 November 2026 — 9,344 subscribers6 November 2026 — 9,352 subscribers8 November 2026 — 9,353 subscribers9,3537 August 20268 November 2026
25 measurements spanning 93 days, net +37. 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 9,303–9,375 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
8 Nov 2026, 23:579,353+1
6 Nov 2026, 03:009,352+8
3 Nov 2026, 01:349,344-3
31 Oct 2026, 09:289,347-3
25 Oct 2026, 18:079,350-4
22 Oct 2026, 19:189,354+12
19 Oct 2026, 04:169,342-9
15 Oct 2026, 22:299,351-2
12 Oct 2026, 13:389,353-9
5 Oct 2026, 18:369,362-1
28 Sept 2026, 14:589,363+1
18 Sept 2026, 22:219,362-1
14 Sept 2026, 19:189,363-4
10 Sept 2026, 20:389,367+12
6 Sept 2026, 04:169,355+6
2 Sept 2026, 04:189,349+1
30 Aug 2026, 10:279,348+5
27 Aug 2026, 04:149,343+20
20 Aug 2026, 22:249,323-3
18 Aug 2026, 03:529,326first reading

Engagement

51 posts held, back to 2 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 50 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
29.0%
avg views ÷ 9,353 subscribers
Avg views / post
2,710
11 posts measured
Reaction rate
1.43%
reactions ÷ views · ER floor
Posts in window
11
of 51 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 10 November 2026
Posts held51 (2 July 2026 – 10 November 2026)
Views total29,830
Reactions total428
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 22:57 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.

What this channel posts

Photos
47
Videos
1
Links
715

Lifetime counters from Telegram’s own channel header, read 10 November 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.

Video runtime
5s
Average length
5s

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

1,776 reactions across 51 posts, in 20 distinct kinds. The most used accounts for 40.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤71440.2%
👍46826.4%
🔥36720.7%
⚡834.67%
❤‍🔥362.03%
👎321.80%
😁281.58%
🤣100.563%
😎80.45%
🗿60.338%
😢60.338%
😭40.225%
👏30.169%
🐳20.113%
🤔20.113%
🤨20.113%
🤬20.113%
💯10.056%
😱10.056%
🤓10.056%

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 51 of the 51 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 1,776 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 51 most recent posts we hold, published 2 July 2026 to 10 November 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 51 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @grokaemcpp. 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 51 most recent posts we hold for this entry, published 2 July 2026 to 10 November 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.

Advertising

Ad load
3.92%
2 of 51 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,360
over 2 measured posts
Median views · rest
3,210
over 49 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFGVnpQA12 November 20262 November 2026
2W5zFJQscAm128 August 202628 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 51 most recent posts we hold, published 2 July 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 11 posts held from the last 30 days (36.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 10:00 UTC≈1,120 views21 reactionsread 10 November 2026

Ссылка внутри std::optional #опытным В прошлом посте была конструкция std::optional<std::reference_wrapper<const Value>>. Зачем так сложно? Почему нельзя было просто std::optional<const Value&>? Дело в том, что в C++17 и далее конструкция std::optional<T&> по стандарту ill-formed программе. И реализации зачастую даже ставили static_assert на ее использование. Проблема была в опасности самой конструкции, а скорее …

🔥10❤6👍5

10 Nov 2026, 07:00 UTC≈1,410 views43 reactionsread 10 November 2026
Photo

Как перейти от ручного управления дроном к командам из собственного кода? Начать можно с наземной станции управления: Python-скрипта, который работает с телеметрией, выполняет проверки перед взлётом и задаёт полётный сценарий. 16 ноября в 20:00 на открытом уроке курса «Разработчик ПО для дронов: ArduPilot, C++ и ROS 2» напишете свою Ground Control Station с помощью Python и MAVSDK. Разберёте, как MAVSDK помогает пр…

👎25😢6❤4🤣3👍2🤬2🗿1

5 Nov 2026, 09:00 UTC≈2,620 views36 reactionsread 10 November 2026

​​LRU-кэш на собеседовании #опытным LRU (Least Recently Used) - классический вопрос на собеседованиях. Вроде не чистый литкоды, можно и ООП пописать, и помикроархитектурить. Но тем не менее задача проверяет знание алгоритмов и структур данных применительно к реально используемой штуке. Требования к задаче: 👉🏿 Реализовать LRU-кэш с фиксированной ёмкостью, задаваемой в конструкторе. 👉🏿 Операции get(key) и put(key, …

👍17❤10🔥6⚡2🤓1

2 Nov 2026, 15:00 UTC≈2,760 views100 reactionsread 10 November 2026

​​С++26. Или все-таки 27? Немного с опозданием, но новость все-таки на канале. Черновик С++26 не удалось утвердить с первого раза на этапе голосования национальных органов ISO. Фактически, принятие С++26 отложено на неопределенный срок. Почему так? Причиной скорее всего являются контракты. По сути, это возможность писать что-то вроде int divide(int a, int b) pre(b != 0) { ... }, где pre — это контракт, проверяемый…

⚡80❤9👍5🗿5🤔1

2 Nov 2026, 12:00 UTC≈2,580 views28 reactionsread 10 November 2026
Advertisementerid 2W5zFGVnpQAPhoto

Экскурсия по лабораториям YADRO: как тестируют серверы и телеком-оборудование В ноябре и декабре YADRO проводит экскурсии по своим лабораториям в Санкт-Петербурге и Москве. На маршрутах — тестовые стенды, оборудование на разных этапах отладки и рабочие пространства команд. Инженеры расскажут, какие проверки проходит железо, и ответят на вопросы. 📍Санкт-Петербург — 12 ноября и 1 декабря 📍Москва — 17 ноября и 8 дека…

👍10❤6🔥6👎5😁1

30 Oct 2026, 09:00 UTC≈3,160 views26 reactionsread 10 November 2026

​​Напишите в комментариях самые запоминающиеся/интересные/сложные вопросы/задачи по С++ с интервью, которые вы проходили. Надеюсь из поста читатели смогут для себя подчерпнуть интересные моменты и найти точки роста, чтобы в следующий раз точно пройти собес. Я начну. Написать потокобезопасную очередь с приоритетом. Приоритета всего 3. Количество тасок с 1 и 2 приоритетом в очереди ограничено, с наименьшим приорите…

🔥13❤8👍3❤‍🔥2

27 Oct 2026, 09:00 UTC≈3,350 views30 reactionsread 10 November 2026

​​Кондвар - это не брокер сообщений #новичкам Думаю, некоторые из вас работали с кафкой и наслаждались ее функционалом. Этот инструмент позволяет в потоке передавать события от продюсера к консюмеру, при этом сохраняя эти события на случай сбоев, необходимости перечитывания или асинхронной работы продюсера и консюмера. Прекрасная технология. И кондвар не реализует практически ничего из этого. Главная ошибка в рассу…

❤15👍6😁6🔥3

24 Oct 2026, 09:00 UTC≈3,280 views45 reactionsread 10 November 2026

​​Какая память быстрее: стек или куча? #новичкам Это довольно общий и не совсем корректный вопрос, но он специально так поставлен, что ответ был чуть более развернутый. Все равно примерно все понимают его смысл. Работа с памятью начинается с ее выделения. Вот у нас ничего не было и мы захотели создать объект на стеке и в куче. Что будет быстрее? int main() { std::vector<int> vec; std::unique_ptr<std::vecto…

❤25😎8👍6🔥6

20 Oct 2026, 09:00 UTC≈3,400 views27 reactionsread 10 November 2026

​​std::atomic::wait под капотом #опытным В C++20 у атомиков появились wait и notify_one/all. void atomic::wait( T old, std::memory_order order = std::memory_order_seq_cst ) const noexcept; void atomic::notify_one() noexcept; void atomic::notify_all() noexcept; Обычно атомики - это про спинлоки и горячие циклы, а тут какой-то интерфейс аля кондвар. В доке написано, что метод wait блокируется ,…

❤12🔥8👍7

17 Oct 2026, 09:00 UTC≈3,210 views37 reactionsread 10 November 2026

Оптимистичные и пессимистичные блокировки #опытным Концепция блокировок уходит далеко за пределы языковых примитивов синхронизации. Блокировки актуальны в принципе для любых систем, с которыми можно работать конкурентно. И идейно для таких систем существует 2 типа локов: оптимистичные и пессимистичные. Они имеют принципиальные отличия и это важно понимать для того, чтобы корректно оперировать данными и их обновления…

👍21❤9🔥7

14 Oct 2026, 09:00 UTC≈2,940 views35 reactionsread 10 November 2026

​​Что внутри std::condition_variable? #опытным Более менее все знакомы с примитивом синхронизации "условная переменная". При наличии мьютекса она может погрузить поток в сон до тех пор, пока не поступит уведомлении и условие пробуждение не будет истинным. Сильно упрощая, в консюмере ждем события на wait, а в продюсере уведомляем через notify о возникновении события. std::mutex mtx; std::condition_variable cv; bool …

❤18🔥9👍8

12 Oct 2026, 09:00 UTC≈3,330 views41 reactionsread 10 November 2026

​​WAT #новичкам Как вы думаете, результат выражения: bool math = -1 < 1U; будет правдой или ложью? Нормальный человек думает, что математика работает. Но С++ выкидывает ее в мусор и по итогу math == false. #ЧЗХ ? Вместо того, чтобы приводить беззнаковое число к знаковому, С++ делает наоборот. В итоге -1 должен конвертироваться в неотрицательное число. В дополненном коде -1 это 0xFFFFFFFF ака все единички, поэт…

❤24👍9🔥4😭4

Showing the 12 most recent of 51 posts we hold for @grokaemcpp. 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.

Posts edited after publishing

@grokaemcpp edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 November 2026
Most recent edit
10 November 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @grokaemcpp as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
24 August 2026
Median time before seen missing
8 days
Seen missing in the last 30 days
0

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Aug 2026, 10:00 UTCAnonymous Poll427 voters

Какие из утверждений ниже правдивы?

  1. c.func(3.14f); не скомпилируется28%
  2. c.func(123); вызывает #378%
  3. c.func("hello"); вызывает #172%
  4. c.func(3.14f); вызывает #241%
  5. b.func(3.14f); вызывает #272%

The shares total 291%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

20 Jul 2026, 10:00 UTCAnonymous Poll800 voters

Cколько динамических аллокаций будет в коде из поста выше?

  1. 049%
  2. 131%
  3. 217%
  4. 39%
  5. 42%
  6. 52%

The shares total 110%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 51 most recent posts we hold, published 2 July 2026 to 10 November 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Physics.Math.Code
@physics_lib · 146,676
Telegram ranks this channel #25 of 72 here — alongside 71 others — read 13 August 2026
InfoSec Portal
@cybersecinform · 20,042
Telegram ranks this channel #72 of 75 here — alongside 74 others — read 2 October 2026
IT Portal
@IT_Portal · 119,243
Telegram ranks this channel #76 of 78 here — alongside 77 others — read 15 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Грокаем C++” (@grokaemcpp), 9,353 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/grokaemcpp.

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.