Dataset Viewer
Auto-converted to Parquet Duplicate
term
string
alternative_names
string
coined_by
string
coiner_role
string
date_coined
string
platform
string
original_tweet
string
original_tweet_url
string
dictionary_definition
string
merriam_webster_entry
string
core_philosophy
string
key_principle
string
workflow_description
string
paradigm_shift
string
spectrum_nature
string
primary_interaction
string
prompting_strategies
string
debugging_approach
string
evaluation_method
string
trust_model
string
material_disengagement
string
primary_ides
string
ai_coding_assistants
string
cloud_based_tools
string
agentic_tools
string
terminal_agents
string
prompt_to_app_platforms
string
ux_ui_design_tools
string
best_practices
string
prompting_techniques
string
awareness_rate
string
active_practitioners
string
developers_using_ai_assisted
string
daily_users
string
weekly_users
string
new_github_devs_copilot
string
global_ai_tool_usage
string
ycombinator_ai_code
string
subreddit_name
string
subreddit_created
string
subreddit_members
string
subreddit_rank
string
related_subreddits
string
linkedin_posts_analyzed
string
reddit_threads_analyzed
string
interview_studies
string
time_savings
string
increased_output
string
improved_skills
string
enjoyment
string
creativity_boost
string
organizational_support
string
strategic_advantage
string
confidence_rating
string
accessibility
string
speed
string
rapid_prototyping
string
coordination_work
string
planning_complexity
string
technical_debt
string
operational_risks
string
security_concerns
string
security_breach_risk
string
scalability_issue
string
code_quality
string
lack_of_understanding
string
maintenance_gaps
string
testing_gaps
string
skills_development
string
job_security_concern
string
review_gaps
string
no_review_process
string
disclosure_issue
string
replit_data_loss
string
prompt_dependency
string
hallucination_risk
string
one_year_rename
string
distinction_made
string
future_autonomous_software
string
hiring_outlook
string
replacement_belief
string
recommendation_rate
string
established_tech_recommendation
string
academic_papers
string
research_methodology
string
research_finding
string
example_projects
string
github_repos
string
timeline
string
traditional_vs_vibe
string
memes
string
cultural_impact
string
jargon_status
string
historical_precedents
string
data_sources
string
dataset_created
string
dataset_version
float64
total_fields
int64
category
string
license
string
Vibe Coding
["vibecoding", "vibe-coding", "AI-assisted programming", "prompt-driven development"]
Andrej Karpathy
OpenAI Co-founder, former Tesla AI Director
February 2, 2025
X (Twitter)
There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
https://x.com/karpathy/status/1886192184808149383
Writing computer code in a somewhat careless fashion, with AI assistance[reference:0]
Yes - added to Merriam-Webster slang dictionary[reference:1]
Code First, Refine Later - focus on creating the 'vibe' of software rather than detailed code[reference:2]
Describe what you want in plain English; AI figures out the rest[reference:3]
I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works[reference:4]
Shift from writing code line-by-line to guiding an AI assistant to generate, refine, and debug through conversation[reference:5]
Exists on a spectrum from 'Full vibe, no code review' to 'Structured vibe, heavy editing'[reference:6]
Natural language prompts → AI generates code → Human reviews/iterates
Blend of vague high-level directives with detailed technical specifications[reference:7]
Hybrid process combining AI assistance with manual practices[reference:8]
Rapid scanning and application testing[reference:9]
Dynamic and contextual trust developed through iterative verification, not blanket acceptance[reference:10]
Practitioners orchestrate code production mediated through AI while maintaining selective oversight[reference:11]
["Cursor", "Windsurf Editor", "VS Code with AI extensions", "JetBrains IDEs"]
["GitHub Copilot", "Tabnine", "Sourcegraph Cody", "Replit", "Codiga", "Amazon Q Developer", "Codeium", "AskCodi", "CodeRabbit", "Qodo"]
["Bolt.new", "Lovable", "v0 by Vercel", "Replit Agent", "same.dev"]
["Cursor Composer/Agent", "GitHub Copilot Agent mode", "Windsurf", "Mistral Vibe", "Cline extension"]
["Vibe Code (npm)", "Continue.dev"]
["Bolt.new", "Lovable", "Replit"]
["v0", "same.dev"]
["Start from a template or existing repo foundation[reference:12]", "Create a comprehensive plan in markdown before coding[reference:13]", "Use Agent mode for file-wide edits and test generation[reference:14]", "Prompt with specificity - include sample inputs and edge cases[reference:15]", "Keep chats focused - new cha...
["Use 'Think hard', 'Think deep', 'Think longer' for complex tasks[reference:20]", "Provide dependency maps for features spanning 5+ files[reference:21]", "Adhere to DRY, SPOT, SOLID, GRASP, YAGNI principles[reference:22]", "Ask for deep research reports on language best practices[reference:23]"]
94% of surveyed individuals have heard about vibe coding[reference:24][reference:25]
54% actively practice vibe coding[reference:26][reference:27]
83% of developers using AI-assisted vibe coding[reference:28][reference:29]
63.2% use these tools daily[reference:30]
28.2% use them weekly[reference:31]
Nearly 80% of new GitHub developers used Copilot within first week[reference:32]
84% of developers worldwide use or plan to use AI coding tools (up from 76% in 2024)[reference:33]
25% of Winter 2025 Y Combinator batch relied on 95% AI-generated code[reference:34]
r/vibecoding
February 8, 2025 (6 days after term coined)[reference:35]
156,000+ members[reference:36][reference:37]
Top 1% of Reddit communities[reference:38][reference:39]
["r/ChatGPTCoding (~101K members)", "r/vibecodingcommunity", "r/ProgrammerHumor", "r/cursor"]
88 unique posts (25,493 words) analyzed[reference:40]
46 threads (102,741 words) analyzed[reference:41]
11 semi-structured interviews conducted[reference:42]
87% of developers reported time savings[reference:43]
74% said they were building more than before[reference:44]
71% said approach made them better at their job[reference:45]
74% said vibe coding made their work more enjoyable[reference:46][reference:47]
67% said it improved creativity[reference:48][reference:49]
76% supported deploying vibe coding tools across their organization[reference:50][reference:51]
54% believe vibe coding provides strategic advantages for time to market[reference:52]
Average confidence: 3.2 out of 5[reference:53]
Non-software developers can now build working applications[reference:54]
Professionals can explore ideas faster than before[reference:55]
Translate ideas into executable applications within hours or minutes[reference:56]
71% said vibe coding increased coordination work for their team[reference:57]
63% said it made planning and task tracking more complex[reference:58]
55% said vibe coding introduces technical debt[reference:59]
33% said it creates operational risks like downtime or failures[reference:60]
53% consider vibe coding unsuitable for scalability and security[reference:61]
Primary vulnerability - lack of proper security protocols[reference:62]
Significant human intervention required to develop scalable code[reference:63]
Code quality is wildly inconsistent - features duplicative or incompatible week to week[reference:64]
You don't know what you're running[reference:65]
Maintenance and scalability challenges[reference:66]
Quality, testing and verification gaps[reference:67]
67% said vibe coding limits learning opportunities for junior developers[reference:68]
39% worried it could threaten their own job security[reference:69]
30% deploy AI-generated code without human review at least some of the time[reference:70]
14% said no additional review process existed at all[reference:71]
40% do not always fully disclose how extensively they use AI tools at work[reference:72]
Replit accidentally wiped a project database without recovery options[reference:73]
Requires very detailed and precise input prompts[reference:74]
Model hallucinations ranked as top concern (17.9%)[reference:75]
On one-year anniversary, Karpathy proposed replacing 'vibe coding' with 'agentic engineering'[reference:76]
Vibe coding = describing what you want and accepting what comes back; Agentic engineering = specifying constraints and using AI to accelerate reasoned implementation[reference:77]
49% believe vibe coding will eventually lead to more autonomous software creation[reference:78]
72% of companies plan to hire the same or more engineers in 2026[reference:79]
70% of leaders disagree that vibe coding will replace core engineering functions[reference:80]
51.4% recommended vibe coding (typically with caveats like 'only for prototyping')[reference:81]
86.7% recommended more established technologies for new entrepreneurs[reference:82]
["Vibe coding: programming through conversation with artificial intelligence (Sarkar & Drosos, 2025)", "Vibe Coding in Practice: Motivations, Challenges, and a Future Outlook \u2013 Grey Literature Review"]
Framework analysis of curated video sessions with think-aloud reflections[reference:83]
Vibe coding does not eliminate need for programming expertise but redistributes it toward context management, rapid code evaluation, and decisions about when to transition[reference:84]
["AI Game created via vibe coding making $50,000/month[reference:85]", "Web3DApp AI Vibe Coding Starter Kit[reference:86]", "NestJS backend template optimized for Cursor[reference:87]", "Elegant Task Management web app built with React and Vite[reference:88]", "BYO-X (Build Your Own X) projects via vibe coding[referenc...
["awesome-vibe-coding (techiediaries) - curated list of tools", "awesome-vibe-coding-guide (analyticalrohit) - best practices", "Vibe-Coding-with-Cursor-A-Complete-Guide (pr0mila)", "vibe-stack - dependency mapping techniques", "vibe-code-boilerplate - workflow orchestration[reference:90]"]
{"2021-2022": "AI autocomplete gets smart - first coding assistants launch[reference:91]", "2023": "Chat enters the editor - LLMs change expectations[reference:92]", "2024": "Agents take the wheel - prompt-to-app platforms emerge[reference:93]", "Feb 2025": "Karpathy coins 'vibe coding' on X[reference:94]", "Feb 8 2025...
{"traditional": "Specify syntax, plan architecture upfront, write line-by-line, deep understanding required[reference:98]", "vibe": "Describe intent in natural language, accept AI output, iterate through conversation, selective oversight[reference:99]"}
["Rick Rubin Headphones meme used to describe vibe coding feeling[reference:100]", "Desert Island meme about being stranded with only AI[reference:101]"]
Term gained traction on conference stages, in job descriptions, and at center of debate about how software gets built[reference:102]
More jargon than slang[reference:103]
Compared to literate programming (Knuth) and egoless programming (Weinberg)[reference:104]
["Merriam-Webster Dictionary\u30108\u3011", "Know Your Meme\u30109\u3011", "Refine.dev blog\u301010\u3011", "arXiv academic paper (Sarkar & Drosos)\u301011\u3011", "MIT Technology Review\u301012\u3011", "GitHub awesome-vibe-coding\u301013\u3011", "GitHub awesome-vibe-coding-guide\u301014\u3011", "Academic grey literatu...
2026-06-16T09:57:46.769442
1
99
AI-Assisted Software Development
CC BY 4.0

Vibe Coding Dataset

This dataset was published on Kaggle by Samyakraj Bayar and mirrored here.

Download

The dataset is available as a ZIP archive: Vibe Coding Dataset.zip

License

MIT

Downloads last month
13