Telegram RegisterThe public register of Telegram
Telegram profile photo for PHP задачи с собеседований

Channel

PHP задачи с собеседований

@phpquiz

On this record: Growth · Engagement · Reactions · Posts · Polls · Cite this entry

2,896subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001243174599
TypeChannel
Username@phpquiz
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/phpquiz

Growth

2,8922,8962,8946 August 2026 — 2,895 subscribers6 August 2026 — 2,895 subscribers7 August 2026 — 2,894 subscribers10 August 2026 — 2,892 subscribers13 August 2026 — 2,894 subscribers20 August 2026 — 2,893 subscribers24 August 2026 — 2,896 subscribers6 August 202624 August 2026
7 measurements spanning 18 days, net +1. 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 2,891–2,897 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 21:142,896+3
20 Aug 2026, 22:422,893-1
13 Aug 2026, 23:142,894+2
10 Aug 2026, 19:562,892-2
7 Aug 2026, 10:142,894-1
6 Aug 2026, 17:162,895no change
6 Aug 2026, 17:072,895first reading

Engagement

20 posts held, back to 26 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.4%
avg views ÷ 2,896 subscribers
Avg views / post
388
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 20 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 5 August 2026
Posts held20 (26 June 20265 August 2026)
Views total1,941
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16: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.

Reaction mix

67 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3247.8%
👍2943.3%
🎉68.96%

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

Measured over the 20 most recent posts we hold, published 26 June 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.

Recent posts

5 Aug 2026, 12:54 UTC225 viewsread 7 August 2026

Один доступ вместо вечного выбора между «нужно для работы» и «давно хотелось изучить» 👇

5 Aug 2026, 07:14 UTC271 viewsread 7 August 2026
Photo

Ваш первый код на Go. Бесплатный урок курса «Go-разработчик. Базовый уровень» Начать изучать новый язык бывает сложно не из-за синтаксиса, а из-за большого количества теории, незнакомых терминов и сложных примеров. В результате многие откладывают обучение, хотя написать первую программу на Go можно уже в первый вечер, если двигаться последовательно и разбираться в основах шаг за шагом. На открытом уроке 10 августа

4 Aug 2026, 07:24 UTC309 viewsread 7 August 2026
Poll

После POST UI должен видеть своё изменение, но проекции обновляются асинхронно. Что корректнее?

  1. Возвращать 200 и сразу читать из проекции19%
  2. Возвращать 202 Accepted + ссылку на статус, пока проекция не догонит83%
  3. Увеличить TTL кеша0%
  4. Синхронно ждать репликации БД10%

The shares total 112%, 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.

29 Jul 2026, 19:39 UTC591 viewsread 7 August 2026
Poll

Почему в доменной логике предпочтительнее DateTimeImmutable, а не DateTime?

  1. Immutable быстрее11%
  2. modify()/add() меняют сам объект, если он расшарен по ссылкам, появляются скрытые баги85%
  3. DateTime не умеет в таймзоны4%
  4. Immutable поддерживает больше форматов7%

The shares total 107%, 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.

27 Jul 2026, 15:33 UTC545 viewsread 7 August 2026

Когда название файла уже само по себе считается техническим долгом 👇

24 Jul 2026, 14:46 UTC672 viewsread 7 August 2026

🎹 До конца июля сохраняются две приятные вещи: специальная цена и бессрочный доступ к материалам курса. Подробнее — в посте 👇

24 Jul 2026, 07:53 UTC730 viewsread 7 August 2026
Poll

Преимущество __serialize()/__unserialize() (PHP 7.4) над __sleep()/__wakeup()?

  1. Быстрее в 10 раз30%
  2. Возвращает/принимает произвольный массив38%
  3. Работает без объявления в классе25%
  4. Автоматически даёт JSON25%

The shares total 118%, 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.

22 Jul 2026, 18:31 UTC691 views6 reactionsread 7 August 2026

💬 Обратная связь Как часто вы проходите собеседования? 🔥 — Сейчас активно ищу работу 👍🏼 — Раз в несколько месяцев ❤️ — Раз в полгода-год 😁 — Не прохожу, уже работаю/ещё учусь

🔥6

19 Jul 2026, 09:54 UTC820 viewsread 7 August 2026
Poll

strlen("привет") при UTF-8 вернёт:

  1. 639%
  2. 1250%
  3. 03%
  4. Зависит от locale10%

The shares total 102%, 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.

15 Jul 2026, 19:26 UTC874 viewsread 7 August 2026
Poll

Память под opcache.memory_consumption выделяется…

  1. Отдельно на каждый запрос20%
  2. Один раз в разделяемой памяти (SHM), общая для всех воркеров пула FPM62%
  3. Копированием в каждый воркер10%
  4. В сессии пользователя8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Jul 2026, 12:21 UTC760 viewsread 7 August 2026
Poll

В чём разница self::FOO и static::FOO при обращении к константе класса?

  1. Разницы нет3%
  2. self:: — класс, где физически написан код; static:: — класс вызова (позднее статическое связывание)89%
  3. static:: для констант запрещён6%
  4. self:: работает только внутри трейтов3%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

12 Jul 2026, 20:37 UTC702 views26 reactionsread 7 August 2026

💬 Обратная связь Проверяем динамику роста комьюнити :) Ваш текущий грейд: 🔥 — Senior 👍🏼 — Middle ❤️ — Junior 😁 — Ещё учусь

🔥14👍10🎉2

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

Polls

The 6 most recent of 12 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, 07:24 UTCAnonymous Poll42 voters

После POST UI должен видеть своё изменение, но проекции обновляются асинхронно. Что корректнее?

  1. Возвращать 200 и сразу читать из проекции19%
  2. Возвращать 202 Accepted + ссылку на статус, пока проекция не догонит83%
  3. Увеличить TTL кеша0%
  4. Синхронно ждать репликации БД10%

The shares total 112%, 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.

29 Jul 2026, 19:39 UTCAnonymous Poll84 voters

Почему в доменной логике предпочтительнее DateTimeImmutable, а не DateTime?

  1. Immutable быстрее11%
  2. modify()/add() меняют сам объект, если он расшарен по ссылкам, появляются скрытые баги85%
  3. DateTime не умеет в таймзоны4%
  4. Immutable поддерживает больше форматов7%

The shares total 107%, 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.

24 Jul 2026, 07:53 UTCAnonymous Poll61 voters

Преимущество __serialize()/__unserialize() (PHP 7.4) над __sleep()/__wakeup()?

  1. Быстрее в 10 раз30%
  2. Возвращает/принимает произвольный массив38%
  3. Работает без объявления в классе25%
  4. Автоматически даёт JSON25%

The shares total 118%, 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.

19 Jul 2026, 09:54 UTCAnonymous Poll137 voters

strlen("привет") при UTF-8 вернёт:

  1. 639%
  2. 1250%
  3. 03%
  4. Зависит от locale10%

The shares total 102%, 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.

15 Jul 2026, 19:26 UTCAnonymous Poll60 voters

Память под opcache.memory_consumption выделяется…

  1. Отдельно на каждый запрос20%
  2. Один раз в разделяемой памяти (SHM), общая для всех воркеров пула FPM62%
  3. Копированием в каждый воркер10%
  4. В сессии пользователя8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Jul 2026, 12:21 UTCAnonymous Poll121 voters

В чём разница self::FOO и static::FOO при обращении к константе класса?

  1. Разницы нет3%
  2. self:: — класс, где физически написан код; static:: — класс вызова (позднее статическое связывание)89%
  3. static:: для констант запрещён6%
  4. self:: работает только внутри трейтов3%

Shares as published, totalling 101%. 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 20 most recent posts we hold, published 26 June 2026 to 5 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.

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

“PHP задачи с собеседований” (@phpquiz), 2,896 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/phpquiz.

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.