2.6 KiB

Raw Blame History

Research Index

Working file for methodology clustering and validation.

Source

perplexity-terminology-research.md — original Perplexity research (Jan 2025)

Methodology Clusters

Tier 1: Must Include (High Authority + High Relevance)

Term	Source Authority	Link Status	Include?
Vibe Coding	Wikipedia, Collins Dictionary, Andrej Karpathy	⏳ verify
Spec-Driven Development	GitHub, ThoughtWorks, Martin Fowler	⏳ verify
AI-Driven Development Life Cycle	AWS	⏳ verify
Agentic Coding	arXiv, AI Accelerator Institute	⏳ verify
AI Pair Programming	GitHub/Microsoft, GeeksforGeeks	⏳ verify

Tier 2: Consider (Good Authority)

Term	Source Authority	Link Status	Include?
Architecture-First AI Development	WaveMaker, ITBrief	⏳ verify
Test-Driven Development with AI	Galileo AI, Builder.io	⏳ verify
Human-in-the-Loop (HITL)	Google Cloud, Atlassian	⏳ verify
Prompt-Driven Development	Capgemini, Hexaware	⏳ verify
Quality-First AI Coding	Qodo.ai	⏳ verify

Tier 3: Maybe (Lower Authority / Niche)

Term	Source Authority	Link Status	Include?
Mobbing with AI	Atlassian	⏳ verify
Copilot-Driven Development	Microsoft/GitHub	⏳ verify
Conversational Coding	Google Cloud, arXiv	⏳ verify
Deterministic AI Development	Augment Code	⏳ verify
Ensemble Programming	Kinde.com, Ultralytics	⏳ verify

Tier 4: Skip (Generic / Low Value)

AI-Assisted Coding — too generic, umbrella term
AI-Augmented Development — too generic
Prompt Engineering — separate skill, not methodology
AI Code Review — tool category, not methodology

Interview Questions Bank

Questions to ask Oleg about each methodology

Vibe Coding — "Ты когда-нибудь так работал? Результат?"
Spec-Driven — "Пробовал писать spec перед кодом с AI?"
Agentic — "Как используешь Claude Code в agentic режиме?"
TDD-AI — "Тесты сначала с AI — работает?"
HITL — "Как часто AI делает что-то без твоего OK?"

Henry's Opinions (from interview)

Will be filled during interview

Link Verification Log

Track which links checked and status

Link	Status	Notes

Updated: 2025-01-22