Matt Pocock profile photo

Matt Pocock @mattpocockuk on X (Twitter): stats, voice and strategy

Matt Pocock (@mattpocockuk) is an X (Twitter) creator with 359.1K followers who posts most about AI Agent Orchestration. Across their last 200 posts they average a 1.12% engagement rate and 2.78 posts a day, busiest on Tuesdays.

Hook formulas, weaknesses and how to get their attention. Included in the free trial, then from $49 a month. See pricing

Followers
359.1K
Following
809
Posts on X
36.9K
Engagement rate
1.12%
Posts a day
2.78
Reply share
0%

Counts as of ; averages from @mattpocockuk's last 200 posts. Engagement rate is likes, reposts and replies divided by views, averaged per post. View @mattpocockuk on X

@mattpocockuk is The Analyst

Brings receipts. Every take arrives with data attached.

  • Evidence over vibes
  • Long-form depth
  • Contrarian when earned

One of six archetypes Xpert reads from the published numbers: topics, cadence, reply habits and format mix. It is a heuristic label, not one Matt Pocock chose.

How @mattpocockuk's posts perform

An average @mattpocockuk post gets 1.3K likes, 77 replies and 48 reposts from 143.5K views.

Per post, on average

Likes
1.3K
Reposts
48
Replies
77
Views
143.5K
Median length
176 chars
Posts analyzed
200

Format mix

With media
26%
With links
25%
Ask a question
15%
Part of a thread
0%

Share of @mattpocockuk's last 200 posts. Replies make up 0% of their output.

When does @mattpocockuk post?

@mattpocockuk posts about 2.8 times a day, most often on Tuesdays and between 12:00 and 15:00 UTC. Engagement is steady: 1.12% across the older half of recent posts, 1.11% across the newer half.

Posts by day of week
Sun: 13 posts, Mon: 30 posts, Tue: 33 posts, Wed: 33 posts, Thu: 33 posts, Fri: 32 posts, Sat: 26 posts
Posts by hour (UTC)
00-03: 1 posts, 03-06: 1 posts, 06-09: 25 posts, 09-12: 41 posts, 12-15: 45 posts, 15-18: 38 posts, 18-21: 40 posts, 21-24: 9 posts
Engagement trend

Steady

1.12% to 1.11% (−0.01 pts, flat)

Oldest half of recent posts against the newest half.

The busiest day and window are in amber. Hours are UTC.

What does @mattpocockuk post about?

Most often AI Agent Orchestration (45% of recent posts), then Software Architecture/Fundamentals (25%), Education & Developer Productivity (20%) and Tech Industry Commentary (10%).

AI summary of their voice

Matt speaks with the clinical, high-intensity focus of a professional instructor and software engineer. He is direct, opinionated about 'software fundamentals,' and acts as a pragmatic guide for…

What they post about

AI Agent Orchestration
45%
Software Architecture/Fundamentals
25%
Education & Developer Productivity
20%
Tech Industry Commentary
10%

Words they lean on

  • agent×43 uses
  • skills×41 uses
  • skill×40 uses
  • agents×39 uses
  • work×36 uses

What works for @mattpocockuk

The 'Gardener' Framework

Frames AI coding not as 'replacing programmers' but as a process of curation and hygiene that resonates with experienced devs.

One of 4 patterns. The rest are in the full analysis.

From one of their posts
I'd argue the only thing your team needs are gardeners.

@mattpocockuk's top recent posts

The most-liked of their last 200 posts, with the numbers X reported. Each opens the original.

Matt Pocock

@mattpocockuk ·

This is an extremely good watch. The things that felt novel/interesting to me: 1. Lock down your agents Humans tend to like 'sharp knife' abstractions - that are powerful, but you can cut yourself if your use them wrong. Lauren says agents perform much better in extremely locked-down environments. Abstractions are designed so they can't screw up, and lint rules enforce it. They built a whole internal framework (Dune) to keep the agent on track. That helps optimise agents that don't have a large context window to work productively in your codebase. 2. Create verification infrastructure To trust the results of any agent, you either need to sit and watch it OR have it provide evidence of its improvement. This has always made sense to me, but Lauren really pushes it hard here: - Invest in custom CLI's that let the agent drive the app and measure its performance - Make the app "factory ready" from the get-go - i.e. deployable to an environment where the agent can mess about with it 3. Feature Maps Lauren's software factory (what she calls an 'outer loop') often requires the agent to break down vague bug reports from users and to turn those into potential fixes. To aid that, they built a 'feature map' of all the main features in their application, which describe exactly how the app is supposed to function. This has become essential for helping the agent navigate the codebase, and figure out quickly how things are supposed to work. It's maintained along with the codebase, and kept in sync via automations. This is the kind of documentation I usually warn against. It goes stale quickly and can confuse agents if it's not kept up to date. But Lauren's team are using it as critical navigation infrastructure, and it makes it possible for agents to explore faster and better - even on a large codebase. So it sounds like navigation docs like this are worth it if they enable new behavior. Banger talk - watch the whole thing on 2x.

135 replies396 reposts5.9K likes645.1K views

What the full analysis adds

The full analysis of @mattpocockuk goes past the public numbers: the hooks they rely on, the patterns that work, the weaknesses holding the account back, and how to get their attention.

The rest of @mattpocockuk's analysis

  • 5 opening-hook formulas, as reusable templates
  • 3 more what-works patterns with real quotes
  • 3 weaknesses holding the account back
  • How to get their attention: what to reply to, in what tone
  • 6 more top posts plus cadence detail
Unlock the full analysis

Included in the free trial, then from $49 a month. Card required, cancel anytime.

The blurred text is a placeholder, not @mattpocockuk's analysis. The real one stays on our server until you unlock it.

Matt Pocock (@mattpocockuk) X (Twitter) Stats, Archetype & Strategy | Xpert