Channel
@mattpocockuk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002607425555 |
|---|---|
| Type | Channel |
| Username | @mattpocockuk |
| Description | I teach devs for a living. Author of Total TypeScript and Al Hero. Ex-@vercel. Used to be a voice coach. |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mattpocockuk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:30 | 12 | no change |
| 6 Aug 2026, 22:37 | 12 | first reading |
20 posts held, back to 9 August 2025 — 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 20 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👍 | 1 | 50.0% |
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 3 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 2reactions 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 9 August 2025 to 13 July 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.
One clarification for folks using /wayfinder: The flow for big work should be: /wayfinder -> /to-spec -> /to-tickets -> /implement Once the /wayfinder map is complete, you turn it into a spec. Some folks are using /wayfinder as the ENTIRE flow - from grilling to prototyping to shipped work It certainly can be used that way - I've been doing that for non-coding stuff like course creation. But for coding I much p…
❤1
I don't really like the "extra-curricular" aspect of this. It works for me because I choose my working hours, but a video briefing might work better.
Thinking about a workflow like this for helping prevent comprehension debt on a fast-moving repo: Fast-moving repo w/lots of changes -> once per day/week, grab a diff of the changes -> feed it to an LLM to output a podcast transcript, focusing on the 'why' of what changed more than the 'what -> feed the podcast transcript to a TTS API -> publish to a private podcast feed -> listen on your commute/morning run/lunch b…
A junior just asked me "what do I do if I'm being grilled about something I don't understand?" Try this: 1. In a grilling session 2. "I don't understand this" 3. "/handoff to a teaching agent to understand this" 4. Pick up the handoff doc with the /teach skill, in your teaching workspace 5. Learn it 6. Go back to the grilling session and pick up where you left off Keeps the grilling session clean, records progress…
Someone DM'd me saying they're using /grill-me in technical interviews Watch the candidate work. See how they answer questions and push back. See whether the AI drives them, or they drive the AI. Honestly genius
👍1
The only exception are things that the code cannot explain itself, like alternatives considered or domain language. I.e. ADR's and glossaries
1. Delete the docs you create to explain your code 2. Take the tokens you save on updating those docs 3. Spend them on making your code self-explanatory
Reworded /grill-me so it can now truly be used anywhere - not just engineering. "design tree" -> "decision tree" "every aspect of this plan" -> "every aspect of this" "codebase" -> "environment" "Do not enact the plan" -> "Do not act on it" https://github.com/mattpocock/skills/pull/532
I feel like I've developed a clear rationale for when to /compact, when to /clear, and when to /handoff But I'm having trouble articulating it. So, what's your mental model for when to do each?
Proposal: a /research skill It's really simple - just spins up a background agent to look at high-trust sources, and saves them in a markdown file. Worth keeping? Or pure no-op? https://github.com/mattpocock/skills/pull/409
Or /wayfinder
I'm working on a new skill which helps you plan enormous chunks of work, far larger than /grill-me can It identifies the frontier of decisions and where the fog of war is It suggests prototyping, research or grilling depending on what the decision is As you push back the fog of war it reveals more decisions It scopes down every decision so it fits in a separate context window (for maximum parallelisation) But I …
Showing the 12 most recent of 20 posts we hold for @mattpocockuk. 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 — 885,577 of 1,340,412entries 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.
Named by 3 registered channels — 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Matt Pocock” (@mattpocockuk), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/mattpocockuk.
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.