Lesson plan

Vibe coding

via voice to text Vibe coding is the software development practice assisted by artificial intelligence (AI) where the software developer describes a project or task in natural languages to a large language model (LLM), which generates source code automatically. Vibe coding may involve accepting AI-generated code without thorough review of the output, instead relying on results and follow-up prompts to guide changes. The term was coined in February 2025 by computer scientist Andrej Karpathy, a co-founder of OpenAI and former AI leader at Tesla. In March 2025, Merriam-Webster listed the term as a "slang & trending" expression. It was also named the Collins English Dictionary Word of the Year for 2025. Advocates of vibe coding say it allows amateur programmers to produce software without the extensive training and skills required for software engineering. Critics say there is a lack of accountability, maintainability, and an increased risk of introducing security vulnerabilities in the resulting software.

Back to article

Article summary

via voice to text Vibe coding is the software development practice assisted by artificial intelligence (AI) where the software developer describes a project or task in natural languages to a large language model (LLM), which generates source code automatically. Vibe coding may involve accepting AI-generated code without thorough review of the output, instead relying on results and follow-up prompts to guide changes. The term was coined in February 2025 by computer scientist Andrej Karpathy, a co-founder of OpenAI and former AI leader at Tesla. In March 2025, Merriam-Webster listed the term as a "slang & trending" expression. It was also named the Collins English Dictionary Word of the Year for 2025. Advocates of vibe coding say it allows amateur programmers to produce software without the extensive training and skills required for software engineering. Critics say there is a lack of accountability, maintainability, and an increased risk of introducing security vulnerabilities in the resulting software.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.