tweet-angle-templates

TIL while working on [project/feature]:

[Specific insight]

[Optional: code snippet or context]

I always assumed [common belief].

Turns out [actual finding] when you [context].

[Evidence or example]

[Technology] tip:

[One-liner tip]

Example:
[code or command]

Problem: [Pain point in one line]

Solution: [What you built/did]

[Optional: Brief how]

Before: [Old approach - pain]
After: [New approach - gain]

The fix: [What changed]

Spent [time] debugging [symptom].

Root cause: [Unexpected thing]

Fix: [Solution]

Lesson: [What to check next time]

3 hours debugging "[error message]"

Tried:
❌ [Thing 1]
❌ [Thing 2]
❌ [Thing 3]

Actual cause: [Surprising root cause]

Check this first next time.

Debugging story:

Symptom: [What was broken]
Assumed cause: [Complex theory]
Actual cause: [Simple mistake]

Sometimes the bug is [simple explanation].

Started: Fix [simple thing]
Ended up: Rewriting [bigger thing]

Here's what I learned down the rabbit hole 🧵

Chose [Option A] over [Option B] for [context]:

✅ [Advantage 1]
✅ [Advantage 2]
⚠️ [Tradeoff accepted]

Would choose differently if [different context].

When to use [Pattern A] vs [Pattern B]:

[Pattern A]: [Use case]
[Pattern B]: [Different use case]

In my case: [What you chose and why]

For [project type], my stack:

• [Tool 1] - [one-line why]
• [Tool 2] - [one-line why]
• [Tool 3] - [one-line why]

Optimizing for [main constraint].

After [time period] with [tool]:

✅ [Pro 1]
✅ [Pro 2]
❌ [Con 1]
❌ [Con 2]

Use it if: [Ideal use case]
Skip it if: [Anti-use case]

Migrated from [Tool A] to [Tool B]:

Worth it? [Yes/No/Depends]

The good: [Benefit]
The bad: [Cost]
The ugly: [Surprise]

[Tool A] vs [Tool B] for [use case]:

[Tool A]: [One-line characterization]
[Tool B]: [One-line characterization]

I went with [choice] because [reason].

Shipped: [Feature name]

What it does: [One line]

The interesting part: [Technical detail]

[Link or screenshot]

[Project] progress update:

✅ [Completed thing 1]
✅ [Completed thing 2]
🔄 Working on: [Current focus]
📋 Next: [Upcoming]

[Project/Feature] milestone:

• [Metric 1]: [Number]
• [Metric 2]: [Number]
• [Metric 3]: [Number]

[Brief context on what this means]

[Project] v[X.Y.Z] released:

• [Feature/fix 1]
• [Feature/fix 2]
• [Feature/fix 3]

Breaking changes: [Yes/No + brief if yes]

[Link]

After [experience], hot take:

[Your opinion]

[Why based on your experience]

Unpopular opinion: [Statement]

I've tried [alternatives].

[Your reasoning] makes [your choice] better for [context].

Change my mind.

[Common practice] is often wrong.

What works better: [Your alternative]

Proof: [Evidence from your work]

Building [feature/project] from scratch 🧵

Goal: [What you're making]
Why: [Motivation]

Let's go →

How [technology/pattern] actually works 🧵

I spent [time] implementing it from scratch.

Here's what I learned →

How to [accomplish task] in [technology]:

A step-by-step thread 🧵

Prerequisites: [What you need]

Let's start →

We shipped [thing] last week.

Here's what went right, wrong, and what I'd do differently 🧵

Genuine question for [audience]:

[Your question]

Context: [Why you're asking]

Reply with your approach.

[Question about preference/approach]

Reply with:
🅰️ [Option A]
🅱️ [Option B]
🆎 [Option C]
🅾️ Other (explain)

[Technology/Pattern] users:

What's your biggest gotcha?

I'll start: [Your example]