3.7 KiB
| slug | title | author | status | created | updated | content_type | primary_keyword | secondary_keywords | assets_folder | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| beyond-vibe-coding | Beyond Vibe Coding: Professional AI Development Methodologies | henry-technical | outline | 2026-01-22 | 2026-01-23 | explainer | ai coding methodologies |
|
assets/beyond-vibe-coding/ |
Idea
Source: Perplexity research on AI-assisted development terminology (Jan 2026)
Concept: Overview article covering AI coding methodologies landscape. Position vibe coding (Collins Word of Year 2025) as entry point, then survey professional approaches: Spec-Driven Development, Agentic Coding, AI Pair Programming, HITL, TDD+AI.
Goal: Establish Henry's expertise in AI-assisted development. Second article for Dev.to account warmup.
Angle: Survey + practitioner perspective (via interview with Oleg)
Brief
See brief.md for complete strategic context, target reader analysis, content requirements, and success criteria.
Quick Summary:
- Goal: Fight "AI is for juniors" stigma with data-backed professional methodologies survey
- Angle: Seniors use AI MORE than juniors (33% vs 13%) — methodology separates pros from beginners
- Format: Survey of 6 methodologies with credentials, practitioner insights, decision framework
- Target: 2,500-3,500 words, thought leadership + long-tail SEO
Outline
See outline.md for complete article structure.
Tone: "Here's what exists and here's what I actually do" — landscape survey through practitioner's lens, not prescriptive guide
Structure:
- Introduction (400w) — Hook with vibe coding, establish legitimacy question
- 6 Methodology sections (400-500w each) — Credentials block, description, Henry's experience (integrated naturally)
- Conclusion (450w) — Landscape overview, legitimacy validation with stats, what I use, community invitation
Total: ~2,800 words Code examples: 3 (CLAUDE.md spec, .claude/settings.json, TDD test)
Assets Index
All working files for this article:
| File | Purpose | Status |
|---|---|---|
| brief.md | Complete Brief: strategic context, target reader, requirements, success criteria | ✅ Complete |
| outline.md | Article structure with word budgets | ✅ Complete |
| ai-usage-statistics.md | Statistical research: AI adoption by seniority, company policies, security concerns | ✅ Complete |
| interview.md | Oleg's practitioner insights — source for Henry's voice | ✅ Complete |
| research-index.md | Methodology clusters, verified sources, interview questions | ✅ Complete |
| log-chat.md | Activity log and agent comments | ✅ Updated |
| text.md | Article draft | ⏳ Pending @writer |
| seo-metadata.md | SEO title, description, keywords | ⏳ Pending @seo |
External Research
| File | Purpose |
|---|---|
| perplexity-chats/AI-Assisted Development_... | Original Perplexity research on terminology |
Activity Log
See log-chat.md
Latest: @architect finalized outline with corrected tone — landscape survey through practitioner lens, not prescriptive guide. Removed "Decision Framework" section, expanded Conclusion to 450w with community engagement. Ready for @validator.