Dev Opinions Scan
Collect and synthesize diverse opinions on specific topics from multiple developer communities.
Purpose
Quickly understand diverse perspectives on technical topics:
- •Distribution of pros/cons
- •Practitioner experiences
- •Hidden concerns or advantages
- •Unique or notable perspectives
Data Sources
| Platform | Method |
|---|---|
| Gemini CLI | |
| Hacker News | WebSearch |
| Dev.to | WebSearch |
| Lobsters | WebSearch |
Execution
Step 1: Topic Extraction
Extract core topic from user request.
Examples:
- •"Developer reactions to React 19" →
React 19 - •"Community opinions on Bun vs Deno" →
Bun vs Deno
Step 2: Parallel Search (Single Message, 4 Sources)
Reddit (Gemini CLI - WebFetch blocked):
bash
gemini -p "Search Reddit for discussions about {TOPIC}. Summarize main opinions, debates, and insights from developers. Include Reddit post URLs where possible."
Other Sources (WebSearch, parallel):
code
WebSearch: "{topic} site:news.ycombinator.com"
WebSearch: "{topic} site:dev.to"
WebSearch: "{topic} site:lobste.rs"
CRITICAL: Run all 4 searches in one message in parallel.
Step 3: Synthesize & Present
3-1. Opinion Classification
Classify collected opinions by:
- •Pro/Positive: Supporting opinions
- •Con/Negative: Concerns, criticism, alternatives
- •Neutral/Conditional: "Only if...", "When used with..."
- •Experience-based: Based on actual production use
3-2. Derive Consensus
Identify opinions repeatedly appearing across communities:
- •Same point mentioned in 2+ sources = consensus
- •Especially high reliability if mentioned in both Reddit and HN
- •Prioritize opinions with specific numbers or examples
- •Target at least 5 consensus items
3-3. Identify Controversies
Find points where opinions diverge:
- •Opposing opinions on same topic
- •Threads with active debates
- •Topics with many "depends on...", "but actually..." responses
- •Target at least 3 controversy points
3-4. Select Notable Perspectives
Find unique or deep insights:
- •Logically sound opinions that differ from majority
- •Opinions from senior developers or domain experts
- •Insights from large-scale project experience
- •Edge cases or long-term perspectives others might miss
- •Target at least 3 notable perspectives
Output Format
Core Principle: All opinions must have inline source. No opinions without sources.
markdown
## Key Insights ### Consensus 1. **[Opinion Title]** - [Detailed description] - Sources: [Reddit](url), [HN](url) 2. **[Opinion Title]** - [Details] - Source: [Dev.to](url) (at least 5) --- ### Controversy 1. **[Controversy Topic]** - Pro: "[Quote]" - [Source](url) - Con: "[Quote]" - [Source](url) - Context: [Why opinions diverge] (at least 3) --- ### Notable Perspective 1. **[Insight Title]** > "[Original quote or key sentence]" - [Why this is notable] - Source: [Platform](url) (at least 3)
Source Citation Rules
- •Inline links required: End every opinion with
Source: [Platform](url) - •Multiple sources:
Sources: [Reddit](url), [HN](url) - •Direct quotes: Use
"..."format when possible - •URL accuracy: Only include verified accessible links
Error Handling
| Situation | Response |
|---|---|
| No search results | Skip that platform, focus on others |
| Gemini CLI failure | Skip Reddit, proceed with other 3 |
| Topic too new | Note insufficient results, suggest related keywords |