{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/8e8dd18b2152422f86aca23ea2c46049\" frameborder=\"0\" width=\"1670\" height=\"1252\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1252,"width":1670,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1252,"thumbnail_width":1670,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/8e8dd18b2152422f86aca23ea2c46049-6520c648660ac008.gif","duration":1299.69,"title":"Understanding the Differences Between Vibe Coding and Enterprise Software Development 🚀","description":"Hey team, in this Loom, I dive into the key differences between vibe coding and fully deploying features in the Polaris platform. I highlight how Daniel and Deepak's vibe coding efforts, while creative, are prototypes rather than the robust enterprise software we need, which involves complex elements like authentication, authorization, and a sophisticated API structure with 743 endpoints. I emphasize that our platform's architecture, including infrastructure as code and CICD practices, is critical for scaling and security. I encourage you both to continue your vibe coding, but remember that it serves as a blueprint rather than the final product. Let's consider turning this discussion into valuable content for our customers to help them understand these concepts better."}