[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ff4rZ6zHkn9cNO3y1GS2KDavSWEt6fWKh10EHmXcwUBI":3,"mdc-131vn-key":32},{"post":4,"related":31},{"id":5,"slug":6,"title":7,"description":8,"content":9,"coverImageUrl":10,"coverImageAlt":10,"tags":11,"featured":15,"tool":10,"status":16,"reviewNote":10,"metaTitle":10,"metaDescription":10,"canonicalUrl":10,"sourceTicketId":10,"agentGenerated":15,"publishedAt":17,"publishedBy":18,"createdAt":19,"updatedAt":19,"authorId":20,"clusterId":21,"ctaId":10,"author":22,"cluster":27,"cta":10},"00000000-0000-4000-e200-000000000002","rise-of-vibe-coding","The Rise of Vibe Coding: What It Means for Teams","Vibe coding is changing how developers approach problems. Here is what engineering managers need to know.","## What Is Vibe Coding?\n\nVibe coding is the practice of working with AI as a creative collaborator rather than treating it as a code completion engine.\n\n## Why Teams Are Adopting It\n\n### Faster Prototyping\n\nTeams using vibe coding report getting from idea to working prototype 3-5x faster.\n\n### Lower Barrier to Contribution\n\nDesigners, PMs, and other non-engineers can meaningfully contribute to codebases.\n\n## The Risks\n\n### Quality Debt\n\nVibe-coded prototypes that ship to production without proper review accumulate technical debt faster.\n\n## Making It Work\n\nThe teams getting the most out of vibe coding treat it as a prototyping tool with a clear handoff to traditional engineering review.",null,[12,13,14],"vibe coding","team productivity","ai workflow",false,"published","2026-05-04T15:39:33.969Z","00000000-0000-4000-a000-000000000001","2026-05-25T15:39:33.995Z","00000000-0000-4000-e100-000000000003","00000000-0000-4000-e000-000000000002",{"slug":23,"name":24,"avatarUrl":10,"role":25,"bio":26},"chinmay-kulkarni","Test Designer","Design Engineer","Design engineer exploring the intersection of AI tooling and developer experience.",{"slug":28,"name":29,"color":30},"vibe-coding","Vibe Coding","#8B5CF6",[],{"data":33,"body":34},{},{"type":35,"children":36},"root",[37,46,52,58,65,70,76,81,87,93,98,104],{"type":38,"tag":39,"props":40,"children":42},"element","h2",{"id":41},"what-is-vibe-coding",[43],{"type":44,"value":45},"text","What Is Vibe Coding?",{"type":38,"tag":47,"props":48,"children":49},"p",{},[50],{"type":44,"value":51},"Vibe coding is the practice of working with AI as a creative collaborator rather than treating it as a code completion engine.",{"type":38,"tag":39,"props":53,"children":55},{"id":54},"why-teams-are-adopting-it",[56],{"type":44,"value":57},"Why Teams Are Adopting It",{"type":38,"tag":59,"props":60,"children":62},"h3",{"id":61},"faster-prototyping",[63],{"type":44,"value":64},"Faster Prototyping",{"type":38,"tag":47,"props":66,"children":67},{},[68],{"type":44,"value":69},"Teams using vibe coding report getting from idea to working prototype 3-5x faster.",{"type":38,"tag":59,"props":71,"children":73},{"id":72},"lower-barrier-to-contribution",[74],{"type":44,"value":75},"Lower Barrier to Contribution",{"type":38,"tag":47,"props":77,"children":78},{},[79],{"type":44,"value":80},"Designers, PMs, and other non-engineers can meaningfully contribute to codebases.",{"type":38,"tag":39,"props":82,"children":84},{"id":83},"the-risks",[85],{"type":44,"value":86},"The Risks",{"type":38,"tag":59,"props":88,"children":90},{"id":89},"quality-debt",[91],{"type":44,"value":92},"Quality Debt",{"type":38,"tag":47,"props":94,"children":95},{},[96],{"type":44,"value":97},"Vibe-coded prototypes that ship to production without proper review accumulate technical debt faster.",{"type":38,"tag":39,"props":99,"children":101},{"id":100},"making-it-work",[102],{"type":44,"value":103},"Making It Work",{"type":38,"tag":47,"props":105,"children":106},{},[107],{"type":44,"value":108},"The teams getting the most out of vibe coding treat it as a prototyping tool with a clear handoff to traditional engineering review."]