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."4metadata:5 version: 1.0.06---78# X/Twitter for Developers910Twitter/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.1112---1314## Before You Start15161. Read `.agents/developer-audience-context.md` if it exists172. Audit your current X presence (bio, pinned, recent posts)183. Understand: Developer Twitter rewards authenticity and technical depth1920---2122## Understanding Dev Twitter2324### Who's on Dev Twitter2526| Segment | What they share | What they consume |27|---------|-----------------|-------------------|28| Open source maintainers | Project updates, war stories | Industry news, peer projects |29| Tech leads | Team learnings, hiring | Architecture, management |30| Indie hackers | Building in public, MRR | Growth tactics, tools |31| DevRel | Content, events, community | Trends, developer sentiment |32| Framework authors | Updates, opinions | Feedback, community vibes |33| Learning devs | Questions, progress | Tutorials, inspiration |3435### What Works on Dev Twitter3637| Content type | Engagement level | Notes |38|--------------|------------------|-------|39| Technical threads | High | Deep dives get saved/shared |40| Code screenshots | High | Visual, scannable |41| Hot takes | High (risky) | Can backfire spectacularly |42| Building in public | High | Journey > destination |43| Memes | Medium-high | Know your audience |44| Announcements | Medium | Better with context |45| Tutorial links | Medium | Need compelling hook |46| Retweets with comment | Low-medium | Add real value |47| Plain links | Low | Algorithm deprioritizes |4849### The Algorithm (As We Understand It)5051| Factor | Impact |52|--------|--------|53| Replies in first hour | High — signals engagement |54| Time spent on post | High — threads > tweets |55| Profile visits from post | High — interesting content |56| Bookmarks | High — "save for later" |57| Retweets | Medium — distribution |58| Likes | Medium — engagement signal |59| Link clicks | Low — X wants you on platform |60| External links | Negative — deprioritized |6162---6364## Thread Structure6566### Thread Anatomy6768```69Tweet 1: HOOK70↓71Tweet 2: Context/Promise72↓73Tweets 3-8: The meat (examples, steps, insights)74↓75Tweet 9: Summary/Takeaway76↓77Tweet 10: CTA + Engagement ask78```7980### Hook Patterns That Work8182| Pattern | Example |83|---------|---------|84| **Contrarian** | "Hot take: You don't need Kubernetes for most apps" |85| **Promise** | "How we reduced our AWS bill by 60% (thread)" |86| **Story** | "Last week our API went down for 4 hours. Here's what happened:" |87| **List tease** | "7 TypeScript tricks that changed how I code:" |88| **Question** | "Why do most startups get database migrations wrong?" |89| **Result** | "We went from 0 to 10K users in 30 days. Here's the playbook:" |9091### Thread Writing Best Practices9293| Element | Guideline |94|---------|-----------|95| **Length** | 5-12 tweets optimal |96| **First tweet** | Hook — no hashtags, no links |97| **Each tweet** | One idea, complete thought |98| **Numbering** | Use X/10 format or emoji bullets |99| **Code** | Screenshots > text (more engaging) |100| **Pacing** | Mix short punchy + longer explanatory |101| **Last tweet** | CTA: follow, reply, bookmark |102103### Thread Template104105```106🧵 [Hook: Compelling statement or question]107108Here's what I learned [context]:1091101/ [First key point]111112[Supporting detail or example]1131142/ [Second key point]115116[Code screenshot or visual]1171183/ [Third key point]119120The counterintuitive part:121122[Insight that surprises]1231244/ [Fourth key point]125126Common mistake to avoid:127128[What not to do and why]1291305/ [Summary]131132TL;DR:133• Point 1134• Point 2135• Point 3136137If this was helpful, give me a follow @handle for more [topic].138139What's your experience with [topic]? 👇140```141142---143144## Code Screenshots145146### Why Screenshots Beat Code Blocks147148| Screenshots | Code blocks |149|-------------|-------------|150| Syntax highlighting | Plain text |151| Control over appearance | Platform formatting |152| Can include context | Just code |153| More visual stops | Scroll past |154| Better engagement | Lower engagement |155156### Code Screenshot Tools157158| Tool | Best for |159|------|----------|160| **Carbon** (carbon.now.sh) | Beautiful, customizable |161| **Ray.so** | Clean, modern |162| **Snappify** | Annotations, animations |163| **CodeSnap** (VS Code) | Quick from editor |164| **Silicon** (CLI) | Automation |165166### Screenshot Best Practices167168| Do | Don't |169|----|-------|170| Use dark theme | Light theme (harder to read) |171| Include file name | Remove context |172| Highlight key lines | Show walls of code |173| Keep width reasonable | Make text tiny |174| Use consistent styling | Different themes per post |175| Add comments in code | Explain separately only |176177---178179## Engagement Timing180181### Best Posting Times182183| Time (PT) | Audience | Notes |184|-----------|----------|-------|185| 6-8 AM | US East Coast + Europe | Morning scroll |186| 10 AM - 12 PM | Peak US | Lunch break |187| 4-6 PM | US evening + Europe late | End of workday |188189### Posting Frequency190191| Frequency | Effect |192|-----------|--------|193| 1-3 tweets/day | Sustainable, quality |194| 3-5 tweets/day | Growth mode |195| 5+ tweets/day | Risk of overexposure |196| 1 thread/week | Good cadence |197| 2-3 threads/week | Aggressive growth |198199### Thread Timing200201- **Post threads** in morning (7-10 AM PT)202- **Engage replies** for first 2 hours203- **Quote tweet** your thread later in day204- **Post follow-up** content same day205206---207208## Hashtags (Use Sparingly)209210### Developer Hashtags211212| Hashtag | Use for |213|---------|---------|214| #buildinpublic | Indie hacker updates |215| #devrel | DevRel content |216| #100DaysOfCode | Learning journey |217| #opensource | OSS announcements |218| #webdev | Web development |219| #javascript #python etc. | Language-specific |220221### Hashtag Rules222223| Do | Don't |224|----|-------|225| Max 1-2 per tweet | Stuff with hashtags |226| Put at end | Lead with hashtags |227| Use for discoverability | Use on every post |228| Skip in threads | Add to every tweet |229230---231232## Building a Dev Following233234### The Flywheel2352361. **Create valuable content** → People engage2372. **Engage with replies** → Build relationships2383. **Reply to others' posts** → Get discovered2394. **Consistency** → Algorithm favors you2405. **Followers grow** → More reach2416. **Repeat**242243### Profile Optimization244245| Element | Best practice |246|---------|---------------|247| **Photo** | Clear face, professional |248| **Name** | Real name (or consistent handle) |249| **Bio** | What you do + what you tweet about |250| **Link** | Your most important URL |251| **Pinned tweet** | Your best/most representative content |252| **Header** | On-brand, not cluttered |253254**Bio formula**:255```256[Role] at [Company/Project]. Building [what].257Tweeting about [topics]. [Credibility signal].258```259260**Examples**:261```262Engineering @ Vercel. Building the web, one component at a time.263Tweeting about React, Next.js, and developer experience.264265Indie hacker. Building saas.com ($10K MRR).266Writing about startups, coding, and building in public.267```268269### Reply Strategy270271| Reply to | Why |272|----------|-----|273| Big accounts in your niche | Visibility to their audience |274| People asking questions you can answer | Demonstrate expertise |275| Your followers | Build relationships |276| Controversial takes | Join the conversation (carefully) |277278**Good reply patterns**:279- Add information they missed280- Share your experience281- Ask thoughtful follow-up282- Respectfully disagree with reasoning283284---285286## What to Avoid (The Cringe Zone)287288### Content That Fails289290| Type | Why it fails |291|------|--------------|292| Humble brags | "So humbled to be named Top 100..." |293| Engagement bait | "Like if you agree!" |294| Empty motivation | "Keep grinding!" |295| Obvious pitches | "Check out our product!" |296| Excessive hashtags | Looks spammy |297| Copied threads | People notice |298| AI-generated slop | Obvious and hollow |299| Thread guys formula | Overused patterns |300301### Behaviors to Avoid302303| Behavior | Why it hurts |304|----------|--------------|305| Buying followers | Fake engagement, obvious |306| Engagement pods | Manipulated, not real reach |307| Aggressive follow/unfollow | Looks desperate |308| DM pitching | Spam, burns bridges |309| Arguing publicly | Rarely looks good |310| Dunking on people | Short-term engagement, long-term reputation |311| Deleting unpopular takes | Own your opinions |312313### The Authenticity Test314315Before posting, ask:3161. Would I say this in person?3172. Is this genuinely useful or interesting?3183. Am I adding to the conversation?3194. Would I respect someone who posted this?320321---322323## Platform-Specific Do's and Don'ts324325### Do's3263271. **Do** share real experiences and learnings3282. **Do** use visuals (code screenshots, diagrams)3293. **Do** engage in first hour after posting3304. **Do** build in public authentically3315. **Do** reply thoughtfully to others3326. **Do** share credit and amplify others3337. **Do** be consistent in posting schedule3348. **Do** have opinions (respectfully)335336### Don'ts3373381. **Don't** be a reply guy with no original content3392. **Don't** use AI to generate generic content3403. **Don't** copy popular threads verbatim3414. **Don't** pitch in DMs uninvited3425. **Don't** use more than 2 hashtags3436. **Don't** post links without context3447. **Don't** be negative/dunking constantly3458. **Don't** automate engagement346347---348349## Content Calendar350351### Weekly Template352353| Day | Content type |354|-----|--------------|355| Monday | Thread (educational) |356| Tuesday | Quick tip or insight |357| Wednesday | Engage/reply heavy |358| Thursday | Share someone else's great content |359| Friday | Personal/behind the scenes |360| Weekend | Optional: light content |361362### Content Mix363364| Type | Percentage |365|------|------------|366| Educational/useful | 50% |367| Personal/journey | 25% |368| Opinions/takes | 15% |369| Promotional | 10% |370371---372373## Tools374375| Tool | Use case |376|------|----------|377| **[Octolens](https://octolens.com)** | Monitor Twitter/X for mentions of your product, competitors, and relevant conversations. Get alerts when people discuss problems you solve. |378| **Carbon** | Beautiful code screenshots |379| **Typefully** | Thread drafting and scheduling |380| **Buffer/Hootsuite** | Scheduling |381| **TweetDeck** | Multi-column management |382| **Followerwonk** | Audience analysis |383384---385386## Thread Checklist387388Before posting:389390- [ ] Hook is compelling (no links, no hashtags)391- [ ] Each tweet is a complete thought392- [ ] Code is in screenshots, not text393- [ ] Thread is 5-12 tweets394- [ ] Summary/TL;DR included395- [ ] CTA at the end396- [ ] Scheduled for optimal time397- [ ] Ready to engage for first 2 hours398399---400401## Related Skills402403- `developer-audience-context` — Know who you're talking to404- `dev-to-hashnode` — Turn threads into blog posts405- `linkedin-technical` — Cross-post for B2B reach406- `hacker-news-strategy` — Drive traffic from X to HN posts
jonathimer