Never run claude /init It'll burn tokens, go out of date in days, and bloat your system prompt. Here's why:
464124514 viral
AI Prompting22 days ago
Back to Discover Heroes
Matt Pocock
LinkedIn Content Strategy & Writing Style
Author of AI Hero
United Kingdom
38 Viral ScoreView on LinkedIn
0 people tracking this creator on Viral Brain
Performance Overview
Followers
64.5K
Connections
1.2K
Avg. Engagement
Top Posts by Engagement
View on LinkedIn
Posting Patterns & Frequency
1.3 posts/week
Posts / Week
5.9 days
Days Between Posts
1
Total Posts Analyzed
MEDIUM
Posting Frequency
Timezone: Europe/London
Best Performing Days
MondayTuesday
Best Performing Times To Post
10:30–11:3011:00–12:00
Topics & Content Focus
Primary Topics
AI-assisted software engineering workflows (from requirements to delegation/agents)Prompt/system-instruction engineering for coding agents (token efficiency, instruction hygiene)Pragmatic codebase design for the AI era (maintainability, cognitive load, modularity)
Secondary Themes
Anti-patterns and operational pitfalls in AI coding toolingTooling opinions and developer ergonomics (package managers, workflow defaults)Creator-led education product marketing (cohort-based course positioning)
Industry Focus
Developer productivity and AI coding toolsSoftware engineering education (cohorts/newsletters) for working engineersB2B/Prosumer technical audience: full-stack/product engineers adopting LLM agents
Content Categories
Contrarian engineering takesTactical how-to and teardown postsFramework synthesis (reducing tool churn into underlying phases)Lightweight humor/memes for developer cultureDirect-response promotion (course/newsletter)
Performance Insights
243%
Avg Engagement Rate
DECREASING
Performance Trend
Best Performing Topics
Specific anti-pattern warnings in AI coding tools (token waste, stale defaults)Developer-experience pain points with actionable fixes (instruction compliance, workflow control)Practical engineering guidance that bridges classic SWE principles to AI workflows
Virality Signals
Shareable imperatives ("Never…") that read like a rule-of-thumbHigh-specificity tooling references that signal insider credibilityHumor + recognizability (developer dialogue) increases repost likelihoodContrarian stance against mainstream AI hype invites debate and sharing
Structure & Quality
120
Avg Length (Words)
HIGH
Depth Level
ADVANCED
Expertise Level
0.82/10
Uniqueness Score
Common Hooks
Contrarian opener that rejects a popular narrative ("Everyone thinks… I disagree")Hard negative imperative ("Never do X")Problem → consequence escalation ("If you do X, you'll get Y")Developer-dialogue/meme setup to frame a common annoyanceOverwhelm compression ("A thousand frameworks… underneath they're all the same")
Common Endings
Newsletter CTA positioned as identity-filtering (anti "vibe coder")Cliffhanger teaching promise ("Here's why" / "Here's how")Direct link drop after framing the pain/insightReassurance + invitation via Q/A mini-FAQ
Value Delivery Methods
Turns AI-tool chaos into stable mental models (phases, principles)Prevents costly mistakes via clear anti-patternsTranslates classic SWE concepts into AI-agent-era practicesProvides immediately actionable workflow adjustments
Formatting Style
Very short paragraphs with strong line breaksQuote-style dialogue blocksEmphasis via blunt sentences and repetitionOccasional Q: / A: structureMinimal bullets; relies on pacing and whitespace
Audience & Tone
YES
Question Usage
0.1%
Response Rate
Detected Tone
Smart-casual technical authorityContrarian pragmatistEngineer-to-engineer mentorSkeptical of hype, bullish on fundamentalsDirect-response marketer with credibility-first framingsemi-formalmixed
Interaction Style
Debate-friendly contrarian framingIdentity alignment (serious engineers vs "vibe coders")Peer-to-peer tacit knowledge exchange (tools, workflows, best practices)Problem-solving orientation ("better way", "here's why")
Community Building Signals
Newsletter as a membership filter and recurring touchpointCohort-based course as a deeper relationship productConsistent in-group language that cultivates engineer community norms
Writing Style Patterns
Content Strategy
Hook: Contrarian opener that rejects a popular narrative ("EveryonTone: semi-formalCTA: Identity-based CTA ("not for vibe coders")
Writing style breakdown
<start of post>
Most developers are using AI to write more code.
That's a mistake. You should be using AI to write less code, but better code.
I've spent the last 3 months perfecting a workflow that does exactly that. I call it the 'Clean Sweep.'
It's not about the prompt. It's about the architecture.
If your modules are shallow, AI will just hallucinate more boilerplate. If your modules are deep, AI becomes a force multiplier.
I'm teaching this entire system in my upcoming workshop.
Sign up here: https://lnkd.in/e4va3qpY
Q: Is this for beginners?
No. This is for engineers who are tired of 'vibe coding' and want to build production-grade systems.
Q: Will I learn how to use Ralph?
Yes. We'll spend 2 hours just on AFK agent delegation. You'll leave with a setup that works while you sleep.
Stop writing more code. Start writing better code.
<end of post>
Sign in to unlock the full writing analysis
Nail your LinkedIn strategy with ViralBrain.
Analyze and write in Matt Pocock's style. Grow your LinkedIn to the next level.