X/Twitter for Developers
Twitter/X remains the real-time pulse of the developer community. This skill covers thread structure, code screenshots, engagement tactics, and building an authentic developer following without being cringe.
Before You Start
- Read
.agents/developer-audience-context.md if it exists
- Audit your current X presence (bio, pinned, recent posts)
- Understand: Developer Twitter rewards authenticity and technical depth
Understanding Dev Twitter
Who's on Dev Twitter
| Segment |
What they share |
What they consume |
| Open source maintainers |
Project updates, war stories |
Industry news, peer projects |
| Tech leads |
Team learnings, hiring |
Architecture, management |
| Indie hackers |
Building in public, MRR |
Growth tactics, tools |
| DevRel |
Content, events, community |
Trends, developer sentiment |
| Framework authors |
Updates, opinions |
Feedback, community vibes |
| Learning devs |
Questions, progress |
Tutorials, inspiration |
What Works on Dev Twitter
| Content type |
Engagement level |
Notes |
| Technical threads |
High |
Deep dives get saved/shared |
| Code screenshots |
High |
Visual, scannable |
| Hot takes |
High (risky) |
Can backfire spectacularly |
| Building in public |
High |
Journey > destination |
| Memes |
Medium-high |
Know your audience |
| Announcements |
Medium |
Better with context |
| Tutorial links |
Medium |
Need compelling hook |
| Retweets with comment |
Low-medium |
Add real value |
| Plain links |
Low |
Algorithm deprioritizes |
The Algorithm (As We Understand It)
| Factor |
Impact |
| Replies in first hour |
High — signals engagement |
| Time spent on post |
High — threads > tweets |
| Profile visits from post |
High — interesting content |
| Bookmarks |
High — "save for later" |
| Retweets |
Medium — distribution |
| Likes |
Medium — engagement signal |
| Link clicks |
Low — X wants you on platform |
| External links |
Negative — deprioritized |
Thread Structure
Thread Anatomy
Tweet 1: HOOK
↓
Tweet 2: Context/Promise
↓
Tweets 3-8: The meat (examples, steps, insights)
↓
Tweet 9: Summary/Takeaway
↓
Tweet 10: CTA + Engagement ask
Hook Patterns That Work
| Pattern |
Example |
| Contrarian |
"Hot take: You don't need Kubernetes for most apps" |
| Promise |
"How we reduced our AWS bill by 60% (thread)" |
| Story |
"Last week our API went down for 4 hours. Here's what happened:" |
| List tease |
"7 TypeScript tricks that changed how I code:" |
| Question |
"Why do most startups get database migrations wrong?" |
| Result |
"We went from 0 to 10K users in 30 days. Here's the playbook:" |
Thread Writing Best Practices
| Element |
Guideline |
| Length |
5-12 tweets optimal |
| First tweet |
Hook — no hashtags, no links |
| Each tweet |
One idea, complete thought |
| Numbering |
Use X/10 format or emoji bullets |
| Code |
Screenshots > text (more engaging) |
| Pacing |
Mix short punchy + longer explanatory |
| Last tweet |
CTA: follow, reply, bookmark |
Thread Template
🧵 [Hook: Compelling statement or question]
Here's what I learned [context]:
1/ [First key point]
[Supporting detail or example]
2/ [Second key point]
[Code screenshot or visual]
3/ [Third key point]
The counterintuitive part:
[Insight that surprises]
4/ [Fourth key point]
Common mistake to avoid:
[What not to do and why]
5/ [Summary]
TL;DR:
• Point 1
• Point 2
• Point 3
If this was helpful, give me a follow @handle for more [topic].
What's your experience with [topic]? 👇
Code Screenshots
Why Screenshots Beat Code Blocks
| Screenshots |
Code blocks |
| Syntax highlighting |
Plain text |
| Control over appearance |
Platform formatting |
| Can include context |
Just code |
| More visual stops |
Scroll past |
| Better engagement |
Lower engagement |
Code Screenshot Tools
| Tool |
Best for |
| Carbon (carbon.now.sh) |
Beautiful, customizable |
| Ray.so |
Clean, modern |
| Snappify |
Annotations, animations |
| CodeSnap (VS Code) |
Quick from editor |
| Silicon (CLI) |
Automation |
Screenshot Best Practices
| Do |
Don't |
| Use dark theme |
Light theme (harder to read) |
| Include file name |
Remove context |
| Highlight key lines |
Show walls of code |
| Keep width reasonable |
Make text tiny |
| Use consistent styling |
Different themes per post |
| Add comments in code |
Explain separately only |
Engagement Timing
Best Posting Times
| Time (PT) |
Audience |
Notes |
| 6-8 AM |
US East Coast + Europe |
Morning scroll |
| 10 AM - 12 PM |
Peak US |
Lunch break |
| 4-6 PM |
US evening + Europe late |
End of workday |
Posting Frequency
| Frequency |
Effect |
| 1-3 tweets/day |
Sustainable, quality |
| 3-5 tweets/day |
Growth mode |
| 5+ tweets/day |
Risk of overexposure |
| 1 thread/week |
Good cadence |
| 2-3 threads/week |
Aggressive growth |
Thread Timing
- Post threads in morning (7-10 AM PT)
- Engage replies for first 2 hours
- Quote tweet your thread later in day
- Post follow-up content same day
Hashtags (Use Sparingly)
Developer Hashtags
| Hashtag |
Use for |
| #buildinpublic |
Indie hacker updates |
| #devrel |
DevRel content |
| #100DaysOfCode |
Learning journey |
| #opensource |
OSS announcements |
| #webdev |
Web development |
| #javascript #python etc. |
Language-specific |
Hashtag Rules
| Do |
Don't |
| Max 1-2 per tweet |
Stuff with hashtags |
| Put at end |
Lead with hashtags |
| Use for discoverability |
Use on every post |
| Skip in threads |
Add to every tweet |
Building a Dev Following
The Flywheel
- Create valuable content → People engage
- Engage with replies → Build relationships
- Reply to others' posts → Get discovered
- Consistency → Algorithm favors you
- Followers grow → More reach
- Repeat
Profile Optimization
| Element |
Best practice |
| Photo |
Clear face, professional |
| Name |
Real name (or consistent handle) |
| Bio |
What you do + what you tweet about |
| Link |
Your most important URL |
| Pinned tweet |
Your best/most representative content |
| Header |
On-brand, not cluttered |
Bio formula:
[Role] at [Company/Project]. Building [what].
Tweeting about [topics]. [Credibility signal].
Examples:
Engineering @ Vercel. Building the web, one component at a time.
Tweeting about React, Next.js, and developer experience.
Indie hacker. Building saas.com ($10K MRR).
Writing about startups, coding, and building in public.
Reply Strategy
| Reply to |
Why |
| Big accounts in your niche |
Visibility to their audience |
| People asking questions you can answer |
Demonstrate expertise |
| Your followers |
Build relationships |
| Controversial takes |
Join the conversation (carefully) |
Good reply patterns:
- Add information they missed
- Share your experience
- Ask thoughtful follow-up
- Respectfully disagree with reasoning
What to Avoid (The Cringe Zone)
Content That Fails
| Type |
Why it fails |
| Humble brags |
"So humbled to be named Top 100..." |
| Engagement bait |
"Like if you agree!" |
| Empty motivation |
"Keep grinding!" |
| Obvious pitches |
"Check out our product!" |
| Excessive hashtags |
Looks spammy |
| Copied threads |
People notice |
| AI-generated slop |
Obvious and hollow |
| Thread guys formula |
Overused patterns |
Behaviors to Avoid
| Behavior |
Why it hurts |
| Buying followers |
Fake engagement, obvious |
| Engagement pods |
Manipulated, not real reach |
| Aggressive follow/unfollow |
Looks desperate |
| DM pitching |
Spam, burns bridges |
| Arguing publicly |
Rarely looks good |
| Dunking on people |
Short-term engagement, long-term reputation |
| Deleting unpopular takes |
Own your opinions |
The Authenticity Test
Before posting, ask:
- Would I say this in person?
- Is this genuinely useful or interesting?
- Am I adding to the conversation?
- Would I respect someone who posted this?
Platform-Specific Do's and Don'ts
Do's
- Do share real experiences and learnings
- Do use visuals (code screenshots, diagrams)
- Do engage in first hour after posting
- Do build in public authentically
- Do reply thoughtfully to others
- Do share credit and amplify others
- Do be consistent in posting schedule
- Do have opinions (respectfully)
Don'ts
- Don't be a reply guy with no original content
- Don't use AI to generate generic content
- Don't copy popular threads verbatim
- Don't pitch in DMs uninvited
- Don't use more than 2 hashtags
- Don't post links without context
- Don't be negative/dunking constantly
- Don't automate engagement
Content Calendar
Weekly Template
| Day |
Content type |
| Monday |
Thread (educational) |
| Tuesday |
Quick tip or insight |
| Wednesday |
Engage/reply heavy |
| Thursday |
Share someone else's great content |
| Friday |
Personal/behind the scenes |
| Weekend |
Optional: light content |
Content Mix
| Type |
Percentage |
| Educational/useful |
50% |
| Personal/journey |
25% |
| Opinions/takes |
15% |
| Promotional |
10% |
Tools
| Tool |
Use case |
| Octolens |
Monitor Twitter/X for mentions of your product, competitors, and relevant conversations. Get alerts when people discuss problems you solve. |
| Carbon |
Beautiful code screenshots |
| Typefully |
Thread drafting and scheduling |
| Buffer/Hootsuite |
Scheduling |
| TweetDeck |
Multi-column management |
| Followerwonk |
Audience analysis |
Thread Checklist
Before posting:
Related Skills
developer-audience-context — Know who you're talking todev-to-hashnode — Turn threads into blog postslinkedin-technical — Cross-post for B2B reachhacker-news-strategy — Drive traffic from X to HN posts
1---2name: x-devs3description: When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for developers."4---56# X/Twitter for Developers78Twitter/X remains the real-time pulse of the developer community. This skill covers thread structure, code screenshots, engagement tactics, and building an authentic developer following without being cringe.910---1112## Before You Start13141. Read `.agents/developer-audience-context.md` if it exists152. Audit your current X presence (bio, pinned, recent posts)163. Understand: Developer Twitter rewards authenticity and technical depth1718---1920## Understanding Dev Twitter2122### Who's on Dev Twitter2324| Segment | What they share | What they consume |25|---------|-----------------|-------------------|26| Open source maintainers | Project updates, war stories | Industry news, peer projects |27| Tech leads | Team learnings, hiring | Architecture, management |28| Indie hackers | Building in public, MRR | Growth tactics, tools |29| DevRel | Content, events, community | Trends, developer sentiment |30| Framework authors | Updates, opinions | Feedback, community vibes |31| Learning devs | Questions, progress | Tutorials, inspiration |3233### What Works on Dev Twitter3435| Content type | Engagement level | Notes |36|--------------|------------------|-------|37| Technical threads | High | Deep dives get saved/shared |38| Code screenshots | High | Visual, scannable |39| Hot takes | High (risky) | Can backfire spectacularly |40| Building in public | High | Journey > destination |41| Memes | Medium-high | Know your audience |42| Announcements | Medium | Better with context |43| Tutorial links | Medium | Need compelling hook |44| Retweets with comment | Low-medium | Add real value |45| Plain links | Low | Algorithm deprioritizes |4647### The Algorithm (As We Understand It)4849| Factor | Impact |50|--------|--------|51| Replies in first hour | High — signals engagement |52| Time spent on post | High — threads > tweets |53| Profile visits from post | High — interesting content |54| Bookmarks | High — "save for later" |55| Retweets | Medium — distribution |56| Likes | Medium — engagement signal |57| Link clicks | Low — X wants you on platform |58| External links | Negative — deprioritized |5960---6162## Thread Structure6364### Thread Anatomy6566```67Tweet 1: HOOK68↓69Tweet 2: Context/Promise70↓71Tweets 3-8: The meat (examples, steps, insights)72↓73Tweet 9: Summary/Takeaway74↓75Tweet 10: CTA + Engagement ask76```7778### Hook Patterns That Work7980| Pattern | Example |81|---------|---------|82| **Contrarian** | "Hot take: You don't need Kubernetes for most apps" |83| **Promise** | "How we reduced our AWS bill by 60% (thread)" |84| **Story** | "Last week our API went down for 4 hours. Here's what happened:" |85| **List tease** | "7 TypeScript tricks that changed how I code:" |86| **Question** | "Why do most startups get database migrations wrong?" |87| **Result** | "We went from 0 to 10K users in 30 days. Here's the playbook:" |8889### Thread Writing Best Practices9091| Element | Guideline |92|---------|-----------|93| **Length** | 5-12 tweets optimal |94| **First tweet** | Hook — no hashtags, no links |95| **Each tweet** | One idea, complete thought |96| **Numbering** | Use X/10 format or emoji bullets |97| **Code** | Screenshots > text (more engaging) |98| **Pacing** | Mix short punchy + longer explanatory |99| **Last tweet** | CTA: follow, reply, bookmark |100101### Thread Template102103```104🧵 [Hook: Compelling statement or question]105106Here's what I learned [context]:1071081/ [First key point]109110[Supporting detail or example]1111122/ [Second key point]113114[Code screenshot or visual]1151163/ [Third key point]117118The counterintuitive part:119120[Insight that surprises]1211224/ [Fourth key point]123124Common mistake to avoid:125126[What not to do and why]1271285/ [Summary]129130TL;DR:131• Point 1132• Point 2133• Point 3134135If this was helpful, give me a follow @handle for more [topic].136137What's your experience with [topic]? 👇138```139140---141142## Code Screenshots143144### Why Screenshots Beat Code Blocks145146| Screenshots | Code blocks |147|-------------|-------------|148| Syntax highlighting | Plain text |149| Control over appearance | Platform formatting |150| Can include context | Just code |151| More visual stops | Scroll past |152| Better engagement | Lower engagement |153154### Code Screenshot Tools155156| Tool | Best for |157|------|----------|158| **Carbon** (carbon.now.sh) | Beautiful, customizable |159| **Ray.so** | Clean, modern |160| **Snappify** | Annotations, animations |161| **CodeSnap** (VS Code) | Quick from editor |162| **Silicon** (CLI) | Automation |163164### Screenshot Best Practices165166| Do | Don't |167|----|-------|168| Use dark theme | Light theme (harder to read) |169| Include file name | Remove context |170| Highlight key lines | Show walls of code |171| Keep width reasonable | Make text tiny |172| Use consistent styling | Different themes per post |173| Add comments in code | Explain separately only |174175---176177## Engagement Timing178179### Best Posting Times180181| Time (PT) | Audience | Notes |182|-----------|----------|-------|183| 6-8 AM | US East Coast + Europe | Morning scroll |184| 10 AM - 12 PM | Peak US | Lunch break |185| 4-6 PM | US evening + Europe late | End of workday |186187### Posting Frequency188189| Frequency | Effect |190|-----------|--------|191| 1-3 tweets/day | Sustainable, quality |192| 3-5 tweets/day | Growth mode |193| 5+ tweets/day | Risk of overexposure |194| 1 thread/week | Good cadence |195| 2-3 threads/week | Aggressive growth |196197### Thread Timing198199- **Post threads** in morning (7-10 AM PT)200- **Engage replies** for first 2 hours201- **Quote tweet** your thread later in day202- **Post follow-up** content same day203204---205206## Hashtags (Use Sparingly)207208### Developer Hashtags209210| Hashtag | Use for |211|---------|---------|212| #buildinpublic | Indie hacker updates |213| #devrel | DevRel content |214| #100DaysOfCode | Learning journey |215| #opensource | OSS announcements |216| #webdev | Web development |217| #javascript #python etc. | Language-specific |218219### Hashtag Rules220221| Do | Don't |222|----|-------|223| Max 1-2 per tweet | Stuff with hashtags |224| Put at end | Lead with hashtags |225| Use for discoverability | Use on every post |226| Skip in threads | Add to every tweet |227228---229230## Building a Dev Following231232### The Flywheel2332341. **Create valuable content** → People engage2352. **Engage with replies** → Build relationships2363. **Reply to others' posts** → Get discovered2374. **Consistency** → Algorithm favors you2385. **Followers grow** → More reach2396. **Repeat**240241### Profile Optimization242243| Element | Best practice |244|---------|---------------|245| **Photo** | Clear face, professional |246| **Name** | Real name (or consistent handle) |247| **Bio** | What you do + what you tweet about |248| **Link** | Your most important URL |249| **Pinned tweet** | Your best/most representative content |250| **Header** | On-brand, not cluttered |251252**Bio formula**:253```254[Role] at [Company/Project]. Building [what].255Tweeting about [topics]. [Credibility signal].256```257258**Examples**:259```260Engineering @ Vercel. Building the web, one component at a time.261Tweeting about React, Next.js, and developer experience.262263Indie hacker. Building saas.com ($10K MRR).264Writing about startups, coding, and building in public.265```266267### Reply Strategy268269| Reply to | Why |270|----------|-----|271| Big accounts in your niche | Visibility to their audience |272| People asking questions you can answer | Demonstrate expertise |273| Your followers | Build relationships |274| Controversial takes | Join the conversation (carefully) |275276**Good reply patterns**:277- Add information they missed278- Share your experience279- Ask thoughtful follow-up280- Respectfully disagree with reasoning281282---283284## What to Avoid (The Cringe Zone)285286### Content That Fails287288| Type | Why it fails |289|------|--------------|290| Humble brags | "So humbled to be named Top 100..." |291| Engagement bait | "Like if you agree!" |292| Empty motivation | "Keep grinding!" |293| Obvious pitches | "Check out our product!" |294| Excessive hashtags | Looks spammy |295| Copied threads | People notice |296| AI-generated slop | Obvious and hollow |297| Thread guys formula | Overused patterns |298299### Behaviors to Avoid300301| Behavior | Why it hurts |302|----------|--------------|303| Buying followers | Fake engagement, obvious |304| Engagement pods | Manipulated, not real reach |305| Aggressive follow/unfollow | Looks desperate |306| DM pitching | Spam, burns bridges |307| Arguing publicly | Rarely looks good |308| Dunking on people | Short-term engagement, long-term reputation |309| Deleting unpopular takes | Own your opinions |310311### The Authenticity Test312313Before posting, ask:3141. Would I say this in person?3152. Is this genuinely useful or interesting?3163. Am I adding to the conversation?3174. Would I respect someone who posted this?318319---320321## Platform-Specific Do's and Don'ts322323### Do's3243251. **Do** share real experiences and learnings3262. **Do** use visuals (code screenshots, diagrams)3273. **Do** engage in first hour after posting3284. **Do** build in public authentically3295. **Do** reply thoughtfully to others3306. **Do** share credit and amplify others3317. **Do** be consistent in posting schedule3328. **Do** have opinions (respectfully)333334### Don'ts3353361. **Don't** be a reply guy with no original content3372. **Don't** use AI to generate generic content3383. **Don't** copy popular threads verbatim3394. **Don't** pitch in DMs uninvited3405. **Don't** use more than 2 hashtags3416. **Don't** post links without context3427. **Don't** be negative/dunking constantly3438. **Don't** automate engagement344345---346347## Content Calendar348349### Weekly Template350351| Day | Content type |352|-----|--------------|353| Monday | Thread (educational) |354| Tuesday | Quick tip or insight |355| Wednesday | Engage/reply heavy |356| Thursday | Share someone else's great content |357| Friday | Personal/behind the scenes |358| Weekend | Optional: light content |359360### Content Mix361362| Type | Percentage |363|------|------------|364| Educational/useful | 50% |365| Personal/journey | 25% |366| Opinions/takes | 15% |367| Promotional | 10% |368369---370371## Tools372373| Tool | Use case |374|------|----------|375| **[Octolens](https://octolens.com)** | Monitor Twitter/X for mentions of your product, competitors, and relevant conversations. Get alerts when people discuss problems you solve. |376| **Carbon** | Beautiful code screenshots |377| **Typefully** | Thread drafting and scheduling |378| **Buffer/Hootsuite** | Scheduling |379| **TweetDeck** | Multi-column management |380| **Followerwonk** | Audience analysis |381382---383384## Thread Checklist385386Before posting:387388- [ ] Hook is compelling (no links, no hashtags)389- [ ] Each tweet is a complete thought390- [ ] Code is in screenshots, not text391- [ ] Thread is 5-12 tweets392- [ ] Summary/TL;DR included393- [ ] CTA at the end394- [ ] Scheduled for optimal time395- [ ] Ready to engage for first 2 hours396397---398399## Related Skills400401- `developer-audience-context` — Know who you're talking to402- `dev-to-hashnode` — Turn threads into blog posts403- `linkedin-technical` — Cross-post for B2B reach404- `hacker-news-strategy` — Drive traffic from X to HN posts
jonathimer