209 lines
7.8 KiB
Markdown
209 lines
7.8 KiB
Markdown
# Research Index
|
||
|
||
Working file for methodology clustering and source verification.
|
||
|
||
## Source Files
|
||
|
||
**Original research:**
|
||
- `perplexity-terminology-research.md` — original Perplexity research (Jan 2025)
|
||
|
||
**Methodology Specs (detailed research per methodology):**
|
||
- [spec-driven-dev.md](spec-driven-dev.md) — GitHub Spec Kit, AWS Kiro, Tessl, Thoughtworks
|
||
- [agentic-coding.md](agentic-coding.md) — arXiv papers, Ralph Loop, Geoffrey Huntley, Cursor 2.0
|
||
- [ai-pair-programming.md](ai-pair-programming.md) — GitHub Copilot official, Microsoft Learn, Cursor
|
||
- [ai-aided-test-first.md](ai-aided-test-first.md) — Thoughtworks Radar, Kent Beck, DORA Report 2025
|
||
|
||
**Statistics:**
|
||
- [ai-usage-statistics.md](ai-usage-statistics.md) — AI adoption by seniority, company policies, security (35+ sources)
|
||
- [ai-adoption-statistics.md](ai-adoption-statistics.md) — LaTeX-formatted data for infographics (2024-2026)
|
||
|
||
---
|
||
|
||
## Methodology Selection
|
||
|
||
Based on research, selecting approaches for article coverage.
|
||
|
||
### Tier 1: MUST Include (High Authority + Reader Interest)
|
||
|
||
| Term | Why Include | Source Authority | Status |
|
||
|------|-------------|------------------|--------|
|
||
| **Vibe Coding** | Hook — Collins Word of Year 2025, everyone knows it | Wikipedia, Collins, Karpathy | ✅ verified |
|
||
| **Spec-Driven Development** | Direct contrast to vibe coding, GitHub Spec Kit | GitHub, ThoughtWorks, Martin Fowler | ✅ verified |
|
||
| **Agentic Coding** | Hot topic, Claude Code users care about this | arXiv surveys (Aug 2025, Dec 2025) | ✅ verified |
|
||
| **Ralph Loop** | HOT Jan 2026, max autonomy extreme | VentureBeat, Geoffrey Huntley, Anthropic plugin | ✅ verified |
|
||
|
||
### Tier 2: SHOULD Include (Good Authority, Practical)
|
||
|
||
| Term | Why Include | Source Authority | Status |
|
||
|------|-------------|------------------|--------|
|
||
| **AI Pair Programming** | Relatable, Copilot users know this | GitHub official, Microsoft | ✅ verified |
|
||
| **Human-in-the-Loop (HITL)** | Important concept, enterprise backing | Atlassian HULA, Google Cloud | ✅ verified |
|
||
| **TDD + AI** | Quality angle, contrasts vibe coding | Qodo.ai, Builder.io, GitHub Blog | ✅ verified |
|
||
|
||
### Tier 3: MENTION Briefly (Context/Completeness)
|
||
|
||
| Term | Why | Status |
|
||
|------|-----|--------|
|
||
| AI-DLC (AWS) | Enterprise angle, shows maturity | ⏳ verify if needed |
|
||
| Architecture-First | 2026 trend prediction | ⏳ verify if needed |
|
||
| Prompt-Driven Development | Clarify difference from vibe coding | ⏳ verify if needed |
|
||
|
||
### Tier 4: SKIP (Generic/Low Value for This Article)
|
||
|
||
- AI-Assisted Coding — umbrella term, too generic
|
||
- AI-Augmented Development — same, no distinct methodology
|
||
- Copilot-Driven Development — subset of AI Pair Programming
|
||
- Conversational Coding — too vague
|
||
- Ensemble Programming — too niche
|
||
- Deterministic AI Development — enterprise-specific, niche
|
||
|
||
---
|
||
|
||
## Article Angle
|
||
|
||
**Narrative arc:**
|
||
1. Vibe coding = entry point (hot topic, word of year)
|
||
2. Problem: works for prototypes, fails for production
|
||
3. Survey: what professionals actually use
|
||
4. Each methodology = one section with:
|
||
- What it is (1-2 sentences)
|
||
- When to use
|
||
- Henry's take (from interview)
|
||
5. Conclusion: spectrum from vibe → spec-driven, choose based on stakes
|
||
|
||
---
|
||
|
||
## Verified Sources
|
||
|
||
### Vibe Coding
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| Wikipedia | en.wikipedia.org/wiki/Vibe_coding | Comprehensive, cites Karpathy |
|
||
| Collins Dictionary | collinsdictionary.com | Word of Year 2025 |
|
||
| Andrej Karpathy | X/Twitter Feb 2025 | Original coiner |
|
||
|
||
### Spec-Driven Development
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| GitHub Spec Kit | github.com/github/spec-kit | Official repo |
|
||
| ThoughtWorks Radar | thoughtworks.com/radar | SDD in techniques |
|
||
| Martin Fowler | martinfowler.com | SDD tools analysis |
|
||
|
||
### Agentic Coding
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| arXiv 2508.11126 | arxiv.org/abs/2508.11126 | "AI Agentic Programming" survey (Aug 2025) |
|
||
| arXiv 2512.07921 | arxiv.org/abs/2512.07921 | "DeepCode: Open Agentic Coding" (Dec 2025) |
|
||
| arXiv 2512.14012 | arxiv.org/html/2512.14012 | "Professional Developers Don't Vibe, They Control" |
|
||
|
||
### Ralph Loop (Ralph Wiggum)
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| Geoffrey Huntley | ghuntley.com/ralph/ | Original author (May 2025) |
|
||
| VentureBeat | venturebeat.com | "How Ralph Wiggum went from Simpsons to AI" (Jan 2026) |
|
||
| GitHub (snarktank) | github.com/snarktank/ralph | Original repo |
|
||
| GitHub (Anthropic) | claude.ai | Official ralph-wiggum plugin by Boris Cherny |
|
||
| Dev.to | dev.to | "2026 - Year of Ralph Loop Agent" |
|
||
|
||
### AI Pair Programming
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| GitHub Features | github.com/features/copilot | "Your AI pair programmer" |
|
||
| GitHub Blog | github.blog (June 2025) | "From pair to peer programmer" |
|
||
| Microsoft Visual Studio | visualstudio.microsoft.com/github-copilot | Official docs |
|
||
| Microsoft Learn | learn.microsoft.com/training/paths/copilot | Training courses |
|
||
|
||
### Human-in-the-Loop
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| Atlassian HULA | atlassian.com/blog/atlassian-engineering/hula-blog | ICSE 2025 paper |
|
||
| arXiv 2411.12924 | arxiv.org/abs/2411.12924 | HULA framework paper |
|
||
| Google Cloud | cloud.google.com/discover/human-in-the-loop | Official definition |
|
||
| Google Developers Blog | developers.googleblog.com | A2A protocol with HITL |
|
||
|
||
### TDD + AI
|
||
| Source | URL | Notes |
|
||
|--------|-----|-------|
|
||
| Qodo.ai | qodo.ai/blog/ai-code-assistants-test-driven-development | AWS SA author |
|
||
| Builder.io | builder.io/blog/test-driven-development-ai | Practical guide |
|
||
| GitHub Blog | github.blog (May 2025) | "TDD with GitHub Copilot" |
|
||
| Substack | ecosystem4engineering.substack.com | "TDD in Age of AI" |
|
||
|
||
---
|
||
|
||
## Interview Questions
|
||
|
||
Questions for Oleg to capture Henry's authentic voice:
|
||
|
||
### Vibe Coding
|
||
- Ты когда-нибудь работал в режиме vibe coding? Что получилось?
|
||
- Когда это уместно, когда нет?
|
||
|
||
### Spec-Driven Development
|
||
- Пробовал GitHub Spec Kit или писать spec перед кодом?
|
||
- Твоё мнение — это будущее или overkill?
|
||
|
||
### Agentic Coding
|
||
- Как используешь Claude Code? Даёшь автономию или контролируешь каждый шаг?
|
||
- Что доверяешь агенту, что нет?
|
||
|
||
### AI Pair Programming
|
||
- Copilot/Cursor — как pair programmer или просто autocomplete?
|
||
- Реально ли это "парное программирование"?
|
||
|
||
### Human-in-the-Loop
|
||
- Как часто AI делает что-то без твоего одобрения?
|
||
- Где граница доверия?
|
||
|
||
### TDD + AI
|
||
- Пишешь тесты первыми при работе с AI?
|
||
- Работает ли классический TDD с генеративным AI?
|
||
|
||
---
|
||
|
||
## Henry's Opinions (from interview)
|
||
|
||
*Will be filled during interview session*
|
||
|
||
### On Vibe Coding
|
||
[pending]
|
||
|
||
### On Spec-Driven Development
|
||
[pending]
|
||
|
||
### On Agentic Coding
|
||
[pending]
|
||
|
||
### On AI Pair Programming
|
||
[pending]
|
||
|
||
### On Human-in-the-Loop
|
||
[pending]
|
||
|
||
### On TDD + AI
|
||
[pending]
|
||
|
||
---
|
||
|
||
*Updated: 2026-01-22*
|
||
|
||
---
|
||
|
||
## TODO: Part 4 Methodologies
|
||
|
||
Potential additions for a fourth part of the series:
|
||
|
||
| Methodology | Research Status | Notes |
|
||
|-------------|-----------------|-------|
|
||
| Architecture-First AI Development | ⏳ Not started | Enterprise/complex systems angle |
|
||
| Prompt-Driven Development | ⏳ Not started | Bridges vibe coding and spec-driven |
|
||
| Copy-pasting from AI chatbot | ⏳ Not started | Baseline methodology, most developers start here |
|
||
|
||
**Research needed:**
|
||
- Source verification for each methodology
|
||
- Interview Oleg for Henry's perspective
|
||
- Keyword research for SEO value
|
||
- Assess if Part 4 justified by volume/interest
|
||
|
||
See main file `3-drafting/beyond-vibe-coding.md` for strategic context.
|