Vibe Coding Framework
  • 💻Introduction
  • 🧠Getting Started
    • Guide for Project Managers
    • Guide for System Owners
  • 🫣Dunning-Kruger Effect
  • Document Organisation
  • Core Concepts
    • What is Vibe Coding
  • Benefits and Challenges
  • Framework Philosophy
  • Security Tools
  • Framework Components
    • Prompt Engineering System
    • Verification Protocols
    • Security Toolkit
    • Documentation Generator
  • Refactoring Tools
  • Team Collaboration
  • Implementation Guide
    • For Individual Developers
  • For Engineering Teams
  • For Enterprises
  • Best Practices
    • Code Review Guidelines
  • Security Checks
  • Documentation Standards
  • Collaboration Workflows
  • Case Studies
    • Success Stories
  • Lessons Learned
  • Examples
    • Enterprise Case Study: Oracle Application Modernisation
    • Local email processing system
  • Resources
    • Tools and Integrations
      • Tools and Integrations Overview
      • Local LLM Solutions
      • Prompt Management Systems
  • Learning Materials
    • Test Your knowledge - Quiz 1
    • Test your knowledge - Quiz 2
  • Community Resources
  • Document Templates
    • AI Assisted Development Policy
    • AI Prompt Library Template
    • AI-Generated Code Verification Report
    • Maintainability Prompts
    • Security-Focused Prompts
    • Testing Prompts
    • [Language/Framework]-Specific Prompts
  • Framework Evolution
    • Versioning Policy
    • Contribution Guidelines
  • Roadmap
  • Glossary of terms
  • Patreon
    • Patroen Membership
  • Contact and Social
  • CREDITS
    • Different tools were used to build this site. Thanks to:
  • The Founder
Powered by GitBook
On this page
  • Why I Created the Vibe Coding Framework
  • My Journey

The Founder

My Name is Kevin Yeandel

PreviousDifferent tools were used to build this site. Thanks to:

Last updated 1 month ago

Why I Created the Vibe Coding Framework

I decided to create the Vibe Coding Framework after noticing a pattern on the web, particularly LinkedIn: discussions about AI-assisted coding (or "vibe coding") were increasingly polarised, with people either overly enthusiastic or dismissively cynical about its potential. I felt this emerging approach was getting unfairly characterised, and as someone who sees genuine value in it, wanted to provide a more balanced perspective.

I believe we're at an inflection point in software development. As AI evolves and context windows expand, we're moving toward a future where fully documented systems can be written and understood by AI - but need to be understood by humans. This doesn't mean the end of human creativity in tech—rather, it shifts our focus to higher-level concerns.

In my view, these AI systems are only as effective as the business and technical requirements presented to them (through well-crafted prompts). The Vibe Coding Framework aims to bridge this gap, providing guidelines for effectively leveraging AI in software development while acknowledging both its current limitations and future potential.

While I believe AI coding will transform developer roles in the longer term, and architectural positions will be augmented by these technologies, I'm concerned about the risks faced by those in the industry who deny these changes. The framework I've created is designed to help technologists embrace this evolution and find their place in this new landscape.

My Journey

My journey in technology spans decades, beginning with a foundation in electronics and a career that started in the defence industry. As a programmer, I've evolved through multiple programming paradigms, starting with Basic and Assembler, then progressing through Pascal, C, C++, and Java. My original trade in electronics provided me with a unique perspective that has proven invaluable in today's IoT landscape, fuelling my continuing passion for automation.

Early in my career, I worked with 8-bit microprocessors, where I developed a knack for reverse engineering ROMs using code I wrote in Borland Turbo Pascal. This hands-on experience with low-level systems gave me insights into computational fundamentals that continue to inform my approach to technology today.

My professional path has included significant work in robotic testing equipment, where I built compilers and interpreters—initially using Flex and Bison before transitioning to ANTLR. During the early 1990s, I was also a contributing writer for EXE magazine, authoring articles about emerging AI technologies, fuzzy logic, and other technical topics well before they became mainstream.

Kevin Yeandel