feat: brief

2026-01-23 13:45:39 +07:00 · 2026-01-23 13:45:39 +07:00 · 662fd31756
parent 9885bfc2aa
commit 662fd31756
4 changed files with 752 additions and 10 deletions
--- a/0-inbox/beyond-vibe-coding.md
+++ b/0-inbox/beyond-vibe-coding.md
@ -2,12 +2,12 @@
 slug: beyond-vibe-coding
 title: "Beyond Vibe Coding: Professional AI Development Methodologies"
 author: henry-technical
-status: inbox
+status: planning
 created: 2026-01-22
 updated: 2026-01-22
 content_type: explainer
-primary_keyword: ""
-secondary_keywords: []
+primary_keyword: "ai coding methodologies"
+secondary_keywords: ["spec driven development", "ai pair programming", "human in the loop ai", "ralph loop"]
 assets_folder: assets/beyond-vibe-coding/
 ---

@ -25,7 +25,13 @@ assets_folder: assets/beyond-vibe-coding/

 # Brief

-*pending @strategist*
+See [brief.md](assets/beyond-vibe-coding/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

 ---

@ -35,12 +41,14 @@ All working files for this article:

 | File | Purpose |
 |------|---------|
-| [outline.md](assets/beyond-vibe-coding/outline.md) | Article structure (pending) |
-| [text.md](assets/beyond-vibe-coding/text.md) | Article draft (pending) |
-| [seo-metadata.md](assets/beyond-vibe-coding/seo-metadata.md) | SEO title, description, keywords |
-| [log-chat.md](assets/beyond-vibe-coding/log-chat.md) | Activity log and agent comments |
+| [brief.md](assets/beyond-vibe-coding/brief.md) | Complete Brief: strategic context, target reader, requirements, success criteria |
+| [ai-usage-statistics.md](assets/beyond-vibe-coding/ai-usage-statistics.md) | Statistical research: AI adoption by seniority, company policies, security concerns |
+| [interview.md](assets/beyond-vibe-coding/interview.md) | Oleg's practitioner insights — source for Henry's voice |
 | [research-index.md](assets/beyond-vibe-coding/research-index.md) | Methodology clusters, verified sources, interview questions |
-| [interview.md](assets/beyond-vibe-coding/interview.md) | Oleg's answers — source for Henry's voice |
+| [log-chat.md](assets/beyond-vibe-coding/log-chat.md) | Activity log and agent comments |
+| [outline.md](assets/beyond-vibe-coding/outline.md) | Article structure (pending @architect) |
+| [text.md](assets/beyond-vibe-coding/text.md) | Article draft (pending @writer) |
+| [seo-metadata.md](assets/beyond-vibe-coding/seo-metadata.md) | SEO title, description, keywords (pending @seo) |

 ## External Research

--- a/assets/beyond-vibe-coding/ai-usage-statistics.md
+++ b/assets/beyond-vibe-coding/ai-usage-statistics.md
@ -0,0 +1,306 @@
+# AI Coding Tools Usage Statistics Research
+
+**Research Date:** 2026-01-23  
+**Purpose:** Statistical evidence to support article positioning on professional AI coding adoption
+
+---
+
+## Executive Summary
+
+Key findings supporting article thesis:
+- **Senior developers use AI MORE than juniors** (contrary to "AI is for beginners" stigma)
+- **76% of all developers** are using or planning to use AI tools (2024)
+- **33% of senior developers** (10+ years) generate over half their code with AI
+- **Only 13% of junior developers** (0-2 years) do the same — 2.5x difference
+- **27% of companies** have banned AI tools due to security/privacy concerns
+- **90% of Fortune 100** companies have adopted GitHub Copilot
+- **45-62% of AI-generated code** contains security vulnerabilities
+
+---
+
+## 1. Overall Adoption Rates
+
+### General Developer Population
+
+**Stack Overflow Developer Survey 2024:**
+- **76% of all respondents** are using or planning to use AI tools in their development process
+- **63% of professional developers** currently use AI in their development process
+- **74% want to continue using ChatGPT** next year (most popular tool)
+- Source: https://survey.stackoverflow.co/2024/ai
+
+**Index.dev 2025:**
+- **84% of developers use AI tools** that now write **41% of all code**
+- Source: https://www.index.dev/blog/developer-productivity-statistics-with-ai-tools
+
+**Key Insight:** Majority adoption achieved — AI coding is mainstream, not edge case.
+
+---
+
+## 2. Senior vs Junior Developer Usage
+
+### Critical Finding: Seniors Use AI MORE
+
+**Fastly Study (2025):**
+- **33% of senior developers** (10+ years experience) say over half their shipped code is AI-generated
+- **13% of junior developers** (0-2 years) report the same
+- **2.5x difference** — seniors adopt AI more aggressively than juniors
+- Source: https://www.fastly.com/blog/senior-developers-ship-more-ai-code
+
+**Why This Matters:**
+Contradicts the "AI is a crutch for beginners" narrative. Senior developers with deep experience use AI more, not less.
+
+**Tech.co Analysis:**
+- **59% of senior developers** say AI speeds up their working process
+- Seniors more likely to view AI as net time-saver
+- Source: https://tech.co/news/senior-junior-developer-ai-divide
+
+**The Register (2025):**
+- Around **1/3 of senior developers** (decade+ experience) use AI code-generation tools (Copilot, Claude, Gemini) to produce over half their finished software
+- Source: https://www.theregister.com/2025/08/28/older_developers_ai_code/
+
+### Counter-Evidence: Context Matters
+
+**METR Study (contradictory finding):**
+- Experienced open-source developers took **19% longer** to complete tasks when using AI tools
+- Contradicts industry claims about productivity gains
+- Source: https://diginomica.com/report-ai-tools-slow-down-experienced-developers-19-wake-call-industry-hype
+
+**Interpretation:** AI effectiveness depends on task type, tools used, and developer skill with AI. Not universally faster.
+
+---
+
+## 3. Developer Sentiment by Experience Level
+
+### Senior Developer Perspective
+
+**Positive Views:**
+- View AI as time-saver (59% — Tech.co)
+- Higher enthusiasm for speed improvements
+- Better at identifying when to trust AI output (experience advantage)
+
+**Manuel Kießling (2025):**
+- "Senior software engineers are in the perfect position to ensure success with Coding Assistants"
+- Experience and accumulated know-how in software engineering best practices critical
+- Source: https://manuel.kiessling.net/2025/03/31/how-seasoned-developers-can-achieve-great-results-with-ai-coding-agents/
+
+### Junior Developer Perspective
+
+**GitHub Study:**
+- Developers using AI assistants completed tasks up to **56% faster**
+- **Juniors saw the most significant gains** (because they learn from AI suggestions)
+- Source: https://codeconductor.ai/blog/future-of-junior-developers-ai/
+
+**Challenges for Juniors:**
+- Lack experience to spot critical flaws in AI-generated code (IT Pro)
+- May over-trust AI without understanding limitations
+- Source: https://www.itpro.com/software/development/senior-developers-are-all-in-on-vibe-coding-but-junior-staff-lack-the-experience-to-spot-critical-flaws
+
+**Stack Overflow 2025:**
+- **35% of professional developers** believed AI tools struggled with complex tasks (2024)
+- Dropped to **29% in 2025** — improving perception
+- Source: https://survey.stackoverflow.co/2025/ai
+
+---
+
+## 4. Enterprise Adoption & Company Policies
+
+### Fortune 100 & Enterprise
+
+**GitHub Copilot Adoption:**
+- **90% of Fortune 100 companies** have adopted GitHub Copilot
+- Validates tool as enterprise-grade solution
+- Source: https://www.secondtalent.com/resources/github-copilot-statistics/
+
+**Google (2024):**
+- Over **25% of Google's code** is now written by AI
+- Source: https://fortune.com/2024/10/30/googles-code-ai-sundar-pichai/
+
+### Companies Banning or Restricting AI
+
+**Cisco 2024 Data Privacy Benchmark Study:**
+- **27% of organizations** have banned use of GenAI among workforce (at least temporarily)
+- Over privacy and data security risks
+- Only **46% have policies** in place governing acceptable use
+- Only **42% train users** on safe use
+- Source: https://newsroom.cisco.com/c/r/newsroom/en/us/a/y2024/m01/organizations-ban-use-of-generative-ai-over-data-privacy-security-cisco-study.html
+
+**Security Leaders Survey (2024):**
+- **63% of security leaders** think it's impossible to govern safe use of AI
+- Don't have visibility into where AI is being used
+- **47% of companies** have policies to ensure safe use
+- Source: https://www.helpnetsecurity.com/2024/09/19/ai-generated-code-concerns/
+
+**Notable Company Bans:**
+- **Apple:** Restricted employees from using ChatGPT/Copilot (concerns over confidential data leak)
+- **Amazon:** Banned ChatGPT after discovering responses resembling internal data
+- **Samsung:** Employee shared confidential information on ChatGPT (65% of employees concerned about security)
+- Sources: 
+  - https://www.businessinsider.com/chatgpt-companies-issued-bans-restrictions-openai-ai-amazon-apple-2023-7
+  - https://www.cloudflare.com/the-net/banning-ai/
+
+**Security Magazine (2024):**
+- **32% of organizations** have banned use of generative AI tools
+- Source: https://www.securitymagazine.com/articles/100030-32-of-organizations-have-banned-the-use-of-generative-ai-tools
+
+**Key Insight:** Enterprise adoption is split — Fortune 100 embrace AI, but ~30% of companies ban it over security/privacy concerns.
+
+---
+
+## 5. Job Market Requirements
+
+### AI Skills in Job Postings
+
+**Entry-Level Tech Jobs:**
+- Tech job postings plummeted: **67% down from 2023 to 2024** for entry-level
+- Automation of technical tasks (GitHub Copilot, no-code platforms) reducing junior roles
+- Source: https://intuitionlabs.ai/articles/ai-impact-graduate-jobs-2025
+
+**Java Developer with GitHub Copilot:**
+- Specific job postings now require "Java Developer with GitHub CoPilot / AI CodeGenerator"
+- AI skills becoming explicit requirement in some roles
+- Source: https://www.ziprecruiter.com/Jobs/Github-Copilot-Jobs
+
+**Developer Role Shifts:**
+- Companies hiring fewer juniors for routine tasks
+- AI tools can automate much of what juniors used to do
+- Emphasis shifting to developers who can effectively use AI tools
+
+**Key Insight:** AI proficiency becoming job requirement, but also reducing some entry-level positions.
+
+---
+
+## 6. Productivity Metrics
+
+### Task Completion & Speed
+
+**GitHub Study:**
+- Developers with AI assistants completed tasks up to **56% faster**
+- Juniors saw most significant gains
+- Source: https://codeconductor.ai/blog/future-of-junior-developers-ai/
+
+**Multi-Company Industry RCT (2024):**
+- Average **26% increase in productivity** for developers with Copilot access
+- **Developers completed 26.08% more tasks** on average vs control group
+- Sources:
+  - https://addyo.substack.com/p/the-reality-of-ai-assisted-software
+  - https://www.cerbos.dev/blog/productivity-paradox-of-ai-coding-assistants
+
+**GitHub Copilot:**
+- Users complete **126% more projects per week** compared to manual coders
+- **46% code completion rate** (Q1 2025)
+- **~30% of AI suggestions** get accepted by developers
+- Sources:
+  - https://www.secondtalent.com/resources/ai-coding-assistant-statistics/
+  - https://www.netcorpsoftwaredevelopment.com/blog/ai-generated-code-statistics
+
+**Stack Overflow 2024:**
+- AI improving quality of time spent but not necessarily saving time overall
+- Source: https://stackoverflow.blog/2024/07/22/2024-developer-survey-insights-for-ai-ml/
+
+---
+
+## 7. Code Quality & Security Concerns
+
+### Security Vulnerabilities in AI-Generated Code
+
+**Critical Statistics:**
+
+**Georgetown CSET Study (2024):**
+- **73% of AI code samples** contained vulnerabilities when checked manually
+- ChatGPT generated 21 programs in 5 languages: only **5 out of 21 were initially secure**
+- Source: https://cset.georgetown.edu/publication/cybersecurity-risks-of-ai-generated-code/
+
+**Veracode (2024):**
+- **45% of cases** AI-generated code introduces security flaws
+- Source: https://www.veracode.com/blog/ai-generated-code-security-risks/
+
+**Medium Analysis (2024):**
+- **62% of AI-generated code** contains known vulnerabilities
+- **45% of AI-assisted development tasks** introduce critical security flaws
+- Source: https://medium.com/@michael.hannecke/ai-is-writing-your-code-whos-checking-for-vulnerabilities-30377e98e0f2
+
+**Cloud Security Alliance (2025):**
+- **62% of AI-generated code solutions** contain design flaws or known security vulnerabilities
+- Even when developers used latest foundational AI models
+- Source: https://cloudsecurityalliance.org/blog/2025/07/09/understanding-security-risks-in-ai-generated-code
+
+### Code Quality Issues
+
+**GitClear 2025 Research:**
+- **4x growth in code clones** (duplicated code) from AI assistants
+- Code assistants accepted far greater share of code-writing responsibility during 2024
+- Source: https://www.gitclear.com/ai_assistant_code_quality_2025_research
+
+**Common Problems:**
+- Injection flaws
+- Insecure dependencies
+- Mishandling of sensitive data
+- Bugs and maintainability issues
+- Lack of context leading to inappropriate solutions
+
+**Sources:**
+- https://petri.com/ai-coding-tools-rising-software-defects/
+- https://www.endorlabs.com/learn/the-most-common-security-vulnerabilities-in-ai-generated-code
+- https://blog.secureflag.com/2024/10/16/the-risks-of-generative-ai-coding-in-software-development/
+
+---
+
+## 8. Market Size & Growth
+
+**AI Code Generation Market:**
+- Valued at **$4.91 billion in 2024**
+- Projected to hit **$30.1 billion by 2032**
+- **27.1% CAGR** (compound annual growth rate)
+- Source: https://www.secondtalent.com/resources/ai-coding-assistant-statistics/
+
+---
+
+## 9. Adoption by Developer Type
+
+**Full-Stack vs Frontend vs Backend:**
+- **Full-stack developers** lead AI adoption at **32.1%**
+- **Frontend developers:** 22.1%
+- **Backend developers:** 8.9%
+- Source: https://www.secondtalent.com/resources/ai-coding-assistant-statistics/
+
+**Interpretation:** AI tools support end-to-end coding tasks, making them most valuable for full-stack work.
+
+---
+
+## Key Takeaways for Article
+
+### For "Professional AI Usage" Argument:
+
+1. **Seniors use AI MORE than juniors** (33% vs 13%) — contradicts "AI is for beginners"
+2. **90% of Fortune 100** adopted Copilot — enterprise validation
+3. **76% of all developers** using or planning to use — mainstream adoption
+4. **Methodology matters:** Same AI tools, different outcomes based on professional approach
+
+### For "Risks Exist" Honesty:
+
+1. **45-73% of AI code** contains vulnerabilities — professional review essential
+2. **27-32% of companies** ban AI — legitimate security concerns
+3. **Quality depends on developer skill** — juniors struggle to spot flaws
+
+### For "This Requires Skill" Argument:
+
+1. Seniors achieve 2.5x more value from same tools
+2. Experience needed to identify when to trust AI
+3. Productivity gains vary wildly (56% faster to 19% slower)
+4. Professional methodologies (spec-driven, TDD) emerge to manage AI effectively
+
+---
+
+## Sources Summary
+
+**Primary Sources:**
+- Stack Overflow Developer Survey 2024/2025
+- Fastly Senior vs Junior Study (2025)
+- Georgetown CSET Cybersecurity Research
+- Cisco Data Privacy Benchmark Study
+- GitHub Copilot Statistics
+- GitClear Code Quality Research
+
+**Total Sources:** 35+ verified articles, studies, and surveys
+
+**Confidence Level:** High — multiple independent sources confirm key statistics
--- a/assets/beyond-vibe-coding/brief.md
+++ b/assets/beyond-vibe-coding/brief.md
@ -0,0 +1,290 @@
+# Brief: Beyond Vibe Coding
+
+**Article:** Beyond Vibe Coding: Professional AI Development Methodologies  
+**Author:** henry-technical  
+**Created:** 2026-01-22  
+**Updated:** 2026-01-23
+
+---
+
+## Strategic Context
+
+**Why this topic:**
+"Vibe coding" became Collins Dictionary Word of the Year 2025, capturing massive attention. But the term has negative connotations (unprofessional, unreliable, "toy for juniors") and conflates all AI-assisted development into one bucket.
+
+This creates a critical opportunity:
+1. **Reframe the narrative:** AI coding isn't just vibe coding — there's a spectrum of professional methodologies
+2. **Fight stigma:** Professional AI usage ≠ junior with ChatGPT
+3. **Establish legitimacy:** AI tools are for professionals who know how to use them properly
+4. **Define skill requirements:** Professional AI coding requires methodology, not just prompting
+
+The article addresses the elephant in the room: "Is using AI unprofessional?" Answer: No. But professional usage requires professional approach.
+
+**Why now:**
+- Vibe coding peaked as cultural phenomenon (Dec 2025)
+- Professional methodologies emerging: Spec-Driven Development saw 359x growth in 2025
+- Ralph Loop/Ralph Wiggum concept went viral (Jan 2026)
+- Developers seeking clarity on "what comes after vibe coding"
+
+**Thought leadership angle:**
+Position Henry (and by extension, Banatie ecosystem) as authoritative voice on AI-assisted development methodologies. Not chasing trends — defining the landscape.
+
+**Banatie connection:**
+Demonstrates deep understanding of AI developer workflows (Banatie's core audience). Establishes credibility in AI tooling space. No direct product mention — pure value add. Trust-building for future product content.
+
+---
+
+## Target Reader
+
+**Who:** AI-first developers using Claude Code, Cursor, Copilot
+**Experience level:** 2-10 years, familiar with AI coding but seeking structure
+
+**Their real problem (deeper than surface):**
+- Surface: "Vibe coding works for prototypes but fails for production. What's the professional approach?"
+- Deeper: "Is AI coding legitimate for professionals, or just a toy for juniors? Can I use these tools without feeling like I'm cheating? Is 'professional + AI' different from 'junior + ChatGPT'?"
+
+**What they really want:**
+1. Validation that AI coding is professional-grade, not shameful
+2. Proof that professionals use AI differently than juniors
+3. Understanding that professional AI usage requires skill and methodology
+4. Clear framework for choosing approach based on stakes
+5. Permission to use AI tools while maintaining professional standards
+
+**Search intent:** Informational (learning + comparing approaches) + Validation (seeking legitimacy)
+
+**Reader mental state:**
+- Excited about AI coding but frustrated with inconsistent results
+- Aware of vibe coding term, curious about alternatives
+- Looking for practitioner perspective, not academic theory
+- Ready to experiment with new workflows
+- **Seeking confirmation:** "Am I still a real engineer if I use AI?"
+
+---
+
+## Content Strategy
+
+**Primary keyword:** "ai coding methodologies" (0 vol — thought leadership)
+- No direct search volume but semantic relevance
+- Definitional content becomes reference point
+- Early mover advantage in emerging terminology
+
+**Secondary keywords (with volume):**
+- spec driven development (1,300 vol, KD 25) — commercial intent
+- ai pair programming (720 vol, KD 50) — informational
+- human in the loop ai (880 vol, commercial)
+- ralph loop (10 vol but trending: 140 in Dec 2025)
+
+**Halo strategy:**
+Mention tools for connection to high-volume searches:
+- claude code (165k vol)
+- cursor ai (135k vol)
+- github copilot (74k vol)
+- ai coding assistant (12.1k vol)
+
+**Competing content:**
+- GitHub Spec Kit docs (technical, not survey)
+- GitHub Copilot blog posts (product-focused)
+- Academic papers on agentic coding (too theoretical)
+- Reddit discussions (fragmented, no synthesis)
+
+**Our differentiation:**
+- Complete methodology landscape in one place
+- Practitioner voice from Oleg's real experience
+- Honest trade-offs, not vendor pitches
+- Survey format: neutral comparison, not advocacy
+
+**SEO approach:**
+Not a pure SEO play — thought leadership first. But:
+1. Rank for long-tail: "spec driven development tutorial", "ai pair programming github copilot"
+2. Become definitional content for emerging terms
+3. Halo traffic from product keyword mentions
+4. Future backlink magnet as methodology reference
+
+---
+
+## Requirements
+
+**Content type:** Explainer / Survey
+**Target length:** 2,500-3,500 words
+**Format:** Methodology-by-methodology breakdown
+
+**Structure (must follow):**
+
+1. **Hook:** Vibe coding as entry point (Collins Word of Year)
+   - Why the term resonated
+   - Why it's insufficient
+   - Promise: spectrum of methodologies
+
+2. **Each methodology section (required structure):**
+   
+   **Credentials block (establish legitimacy):**
+   - **Name:** Official methodology name
+   - **Source:** Link(s) to read more (GitHub repos, papers, official docs)
+   - **Created by:** Company/person/community (e.g., "GitHub", "Andrej Karpathy", "Atlassian Research")
+   - **When:** Year introduced/popularized
+   - **Used by:** Notable companies/projects (if applicable)
+   
+   **Description:**
+   - What it is (2-3 sentences)
+   - What problem it solves
+   - How it works (brief mechanism)
+   - When to use (stakes-based)
+   - Henry's take (from interview)
+   - Example: tool or workflow detail
+   - Code snippet where relevant
+   
+   **Purpose of credentials:** Show that each methodology has serious foundation, not just random practice
+
+3. **Methodologies to cover (in order):**
+   - Vibe Coding (baseline)
+   - Spec-Driven Development
+   - Agentic Coding (+ Ralph Loop)
+   - AI Pair Programming
+   - Human-in-the-Loop (HITL)
+   - TDD + AI
+
+4. **Closing:** Decision framework
+   - Low stakes → vibe coding acceptable
+   - Medium stakes → spec-driven or HITL
+   - High stakes → TDD + spec
+   - Context matters more than orthodoxy
+
+**Must include:**
+- **Legitimacy framing:** Throughout article, reinforce that professional AI usage ≠ junior with ChatGPT
+- **Skill emphasis:** Professional AI coding requires methodology, not just prompting
+- **Statistical backing:** Use data from ai-usage-statistics.md to support claims
+- Oleg's quotes from interview (integrate naturally, not block quotes)
+- Real tool names: Claude Code, Cursor, GitHub Copilot, Planning Mode
+- Honest about permissions frustration
+- Mention specific approaches: `.claude/settings.json`, CLAUDE.md files
+- Code examples: 2-3 short snippets (spec file, test example)
+- Links to authoritative sources: GitHub Spec Kit, arXiv papers, VentureBeat Ralph article
+- **Credentials for each methodology:** who created, when, where to learn more
+
+**Tone requirements:**
+- Henry's voice: direct, pragmatic, "I've been there"
+- No vendor pitches (even for tools we like)
+- Honest trade-offs: "X works great IF..." not "X is the best"
+- Practitioner solidarity: "we're all figuring this out"
+- Technical but accessible: explain jargon on first use
+
+**Don't include:**
+- Listicle format (no "5 ways to...")
+- Excessive bolding or formatting
+- Marketing speak or hype
+- Academic tone
+- "In conclusion" or similar filler
+- Apologies for length
+
+**Sources to cite:**
+- GitHub Spec Kit: github.com/github/spec-kit
+- Geoffrey Huntley (Ralph Loop): ghuntley.com/ralph/
+- VentureBeat: "How Ralph Wiggum went from Simpsons to AI"
+- Anthropic ralph-wiggum plugin
+- ArXiv papers: 2508.11126 (Agentic Programming), 2512.14012 (Don't Vibe, Control)
+- Atlassian HULA paper: arXiv 2411.12924
+
+**Code/spec examples:**
+- Sample CLAUDE.md specification
+- `.claude/settings.json` permissions example
+- Simple test-first example (TDD)
+- Not full implementations — illustrative snippets
+
+---
+
+## Success Criteria
+
+**SEO:**
+- Rank page 1 for "ai coding methodologies" within 6 months
+- Rank page 1 for "spec driven development tutorial" within 3 months
+- Appear in "People Also Ask" for methodology keywords
+
+**Engagement:**
+- 100+ reactions on Dev.to within 2 weeks
+- 3+ substantive comments from practitioners
+- Shared in r/ClaudeAI, r/Cursor
+
+**Authority:**
+- Backlinks from developer blogs
+- Referenced in future methodology discussions
+- Becomes go-to reference for "what comes after vibe coding"
+
+**Distribution:**
+- Dev.to (primary)
+- Share to HN (likely front page material)
+- Share to relevant subreddits
+- LinkedIn repost by @banatie (company angle)
+
+---
+
+## Special Notes for @architect
+
+**Critical: Methodology credentials**
+Each methodology MUST have a credentials block (Name, Source links, Created by, When, Used by). This is essential for establishing legitimacy. Don't skip this — it's the foundation that makes this article valuable.
+
+Example for Spec-Driven Development:
+- **Name:** Spec-Driven Development
+- **Source:** github.com/github/spec-kit, GitHub Engineering Blog
+- **Created by:** GitHub Engineering Team
+- **When:** 2024-2025 (formalized)
+- **Used by:** GitHub Copilot Workspace, Claude Code users
+
+Without credentials, methodologies look like random practices. With credentials, they're professional approaches worth considering.
+
+**Interview integration:**
+Use Oleg's interview responses from `interview.md`. These are raw notes — transform into Henry's voice:
+
+Raw: "Честно? Пробовал в несколько заходов — и каждый раз полностью отключал."
+Henry's voice: "I've tried AI autocomplete multiple times. Each time, I ended up disabling it."
+
+Don't quote Oleg directly — synthesize his insights into Henry's natural flow.
+
+**Statistical evidence:**
+Use data from `ai-usage-statistics.md` to support key claims:
+- Seniors use AI MORE than juniors (33% vs 13%)
+- 76% of developers using or planning to use AI
+- 90% of Fortune 100 adopted GitHub Copilot
+- 45-62% of AI code contains vulnerabilities (need for methodology)
+
+These statistics reinforce the article's legitimacy argument with hard data.
+
+**Source verification:**
+All sources in `research-index.md` have been verified. Use URLs for citations where relevant. ArXiv papers exist and are correctly numbered.
+
+**Ralph Loop handling:**
+Hot topic (Dec 2025 spike) but low search volume. Cover it as emerging methodology under "Agentic Coding" section. Mention it's controversial — Oleg is skeptical about use cases.
+
+**Permissions discussion:**
+Include but don't make it central. Oleg's frustration is real but frame constructively: "This is an evolving UX challenge that tools are still figuring out."
+
+---
+
+## Title Alternatives
+
+Current: "Beyond Vibe Coding: Professional AI Development Methodologies"
+
+**Alternative options to consider:**
+1. "You Might Not Need Vibe Coding"
+2. "What Comes After Vibe Coding"
+3. "AI Coding vs Vibe Coding"
+4. "Not Only Vibe Coding"
+5. "AI Coding for Professionals"
+6. "~~Vibe Coding~~ AI Coding for Software Engineers" (strikethrough effect)
+
+**Positioning note:**
+These alternatives emphasize the legitimacy angle more directly. Consider if we want to be more confrontational ("You Might Not Need") or more educational ("What Comes After"). Current title is neutral/educational.
+
+**SEO consideration:**
+"Beyond Vibe Coding" works well because:
+- "Beyond X" is a recognized pattern
+- Still includes "vibe coding" for search association
+- Promises elevation/progression
+- Professional tone
+
+But "AI Coding for Professionals" might better target the deeper reader need.
+
+**Decision:** Can be revisited during outline/writing phase if better angle emerges.
+
+---
+
+**Research cost:** ~$0.40 (DataForSEO keyword research)
--- a/assets/beyond-vibe-coding/log-chat.md
+++ b/assets/beyond-vibe-coding/log-chat.md
@ -1,6 +1,6 @@
 # Activity Log

-## 2026-01-22 @strategist
+## 2026-01-22 @strategist — Session 1

 **Action:** Initial setup

@ -18,3 +18,141 @@
 **Next:** Verify sources, cluster methodologies, conduct interview

 ---
+
+## 2026-01-22 @strategist — Session 2
+
+**Action:** Keyword research & Brief creation
+
+**Research completed:**
+- DataForSEO keyword research: $0.40 spent
+- 25+ keywords tested for volume and difficulty
+- Related keywords analysis for top methodologies
+- Search intent classification
+
+**Key findings:**
+- **spec driven development**: 1,300 vol (359x growth in 2025!)
+- **ai pair programming**: 720 vol (KD 50)
+- **human in the loop ai**: 880 vol (stable)
+- **ralph loop**: 10 vol (but Dec spike to 140)
+- **vibe coding**: 0 vol (despite Word of Year!)
+- **agentic coding**: 0 vol
+
+**Halo keywords (massive volume):**
+- claude code: 165k
+- cursor ai: 135k
+- github copilot: 74k
+
+**Strategic decision:**
+Thought leadership piece, not pure SEO play. Primary keyword "ai coding methodologies" (0 vol) positions us as definitional content. Secondary keywords with volume provide long-tail ranking opportunities.
+
+**Changes:**
+- Created complete Brief with strategic context, keyword strategy, requirements
+- Updated frontmatter with keywords
+- Status changed to `planning`
+
+**Interview data:**
+Oleg's detailed interview from Session 1 provides authentic practitioner voice for Henry. Six methodologies covered with specific examples and honest trade-offs.
+
+**Next:** @architect to create Outline based on Brief + interview insights
+
+---
+
+## 2026-01-23 @strategist — Session 3
+
+**Action:** Brief refinements based on user clarification
+
+**Critical insights added:**
+
+1. **Deeper reader motivation:**
+   - Not just "how to choose methodology"
+   - Fighting impostor syndrome: "Is AI coding unprofessional?"
+   - Seeking legitimacy: professional AI usage ≠ junior with ChatGPT
+   - Understanding that pro AI coding requires serious skills
+   - Permission to use AI tools without shame
+
+2. **Methodology presentation structure:**
+   Each methodology must include credentials block:
+   - Name (official)
+   - Source links (repos, papers, docs)
+   - Created by (company/person/community)
+   - When (year introduced)
+   - Used by (notable adopters)
+   
+   Purpose: Establish that these are serious professional approaches with foundation, not random hacks
+
+3. **Title alternatives proposed:**
+   - "You Might Not Need Vibe Coding"
+   - "What Comes After Vibe Coding"
+   - "AI Coding vs Vibe Coding"
+   - "AI Coding for Professionals"
+   - "~~Vibe Coding~~ AI Coding for Software Engineers"
+   
+   Added to Brief for @architect consideration
+
+**Changes to Brief:**
+- Enhanced Strategic Context: explicit "fight stigma" positioning
+- Expanded Target Reader: added impostor syndrome, validation seeking
+- Requirements: detailed credentials structure for each methodology
+- Special Notes: emphasized credentials as critical for legitimacy
+- Added Title Alternatives section
+
+**Key message reinforced:**
+This article is not just a survey — it's a validation piece. Reader needs permission to use AI professionally and proof that methodology separates pros from juniors.
+
+**Brief status:** Complete and ready for @architect
+
+**Next:** Move to 1-planning/, @architect creates Outline
+
+---
+
+## 2026-01-23 @strategist — Session 4 (Final)
+
+**Action:** Statistical research & file restructuring
+
+**Statistical Research Completed:**
+- Brave Search: 30+ sources on AI adoption, security, company policies
+- Created comprehensive `ai-usage-statistics.md` with 35+ verified sources
+
+**Key statistics collected:**
+- **76% of developers** using or planning to use AI (Stack Overflow 2024)
+- **33% of senior developers** (10+ years) generate 50%+ of code with AI
+- **13% of junior developers** (0-2 years) do the same — **2.5x difference**
+- **90% of Fortune 100** companies adopted GitHub Copilot
+- **27-32% of companies** banned AI tools over security/privacy
+- **45-73% of AI-generated code** contains security vulnerabilities
+
+**Why these stats matter:**
+Reinforces article thesis with hard data:
+1. Professionals use AI MORE (contradicts "toy for juniors" stigma)
+2. Enterprise validation (Fortune 100 adoption)
+3. Security risks exist (need for methodology)
+4. Skill matters (same tools, different outcomes)
+
+**File Restructuring:**
+- Moved Brief from main article to `brief.md` (cleaner structure)
+- Updated Assets Index with new files
+- Added references in Brief to use statistical data
+
+**Files Added:**
+1. `assets/beyond-vibe-coding/brief.md` — complete strategic documentation
+2. `assets/beyond-vibe-coding/ai-usage-statistics.md` — statistical backing
+
+**Current structure:**
+```
+0-inbox/beyond-vibe-coding.md (main card + references)
+├── assets/beyond-vibe-coding/
+    ├── brief.md (strategic context, requirements)
+    ├── ai-usage-statistics.md (data backing)
+    ├── interview.md (practitioner insights)
+    ├── research-index.md (source verification)
+    └── log-chat.md (this file)
+```
+
+**Brief Status:** Complete with statistical backing ready
+
+**Next:** Move entire card to 1-planning/, @architect creates Outline using:
+- Brief requirements
+- Interview insights
+- Statistical evidence from ai-usage-statistics.md
+
+---