I really appreciate you putting this message out there. I’ve been “vibe coding” to prototype ideas, and I’ve also seen the backlash from very experienced technical leaders - eye-rolls, scoffing, the implicit msg - “that’s not real engineering.” But that reaction misses the point: vibe coding isn’t a replacement for good engineering discipline; it’s a way to compress the distance between an idea and something you can test in less than a day!
Normalizing the mindset of 50% exec, 50% IC and being self sufficient in bringing ones ideas to life is so important👍🏻
Yes on compressing the distance!! The prototype is to validate and communicate the idea - the code can be thrown away, not pushed into production, if that’s the concern. Love the push for self sufficiency and agency.
Love this! I've also been seeing a bunch of posts about using lovable to build a presentation instead of slides, that's definitely on my list of things to try. Most recently I built a feedback analysis tool that takes raw text feedback and converts it into feature requests, usability issues, and bug reports. It's crazy to me how easy it was to build with Lovable, it's super addicting I keep iterating on it.
Great post Elena. Love the North Metric example as something Exec level that can help move the needle. In the past I'm sure our bosses would have delegated this to us to do, but its clear its all hands on the work this decade :)
I love this! I've been vibecoding using Lovable and it's been so fun. For me the primary use case is to see if the ideas that I think are so great are actually any good :) I love the uses cases you mentioned.
I attended a product conference in October and heard a lot about Lovable. I haven’t written code in 30 years but decided to subscribe and start experimenting. I’ve built a complete vision of my product’s future and made it fully functional. Is it perfect? No. Is it changing the conversation with clients and prospects, as well as colleagues, 100%.
Elena, I didn’t even realize the connection between you and Lovable when I started. I just heard a lot about it over the course of a few days. Happy to show you or talk through the experience.
There are so many niche Lovable use cases besides prototypes! I use it to place mockups into an iPhone frame, and to create little animations - it’s wild that it’s easier to do that with code than in some kind of drag and drop design tool.
That said, these are all on the side - I’m yet to clear the hurdle of enterprise IT / legal approval for all these apps at work 😩 I’m trying but it’s slow, and I’m not sure the juice is worth the squeeze.
Vibe coding one-off tools definitely has its merits, but a lack of standardization around tooling, templates, processes, and assets has challenges as a company scales.
Awesome for prototyping a new asset or feature, but becomes annoying when everyone comes up with a net new asset every single time
I really appreciate you putting this message out there. I’ve been “vibe coding” to prototype ideas, and I’ve also seen the backlash from very experienced technical leaders - eye-rolls, scoffing, the implicit msg - “that’s not real engineering.” But that reaction misses the point: vibe coding isn’t a replacement for good engineering discipline; it’s a way to compress the distance between an idea and something you can test in less than a day!
Normalizing the mindset of 50% exec, 50% IC and being self sufficient in bringing ones ideas to life is so important👍🏻
Yes on compressing the distance!! The prototype is to validate and communicate the idea - the code can be thrown away, not pushed into production, if that’s the concern. Love the push for self sufficiency and agency.
Love this! I've also been seeing a bunch of posts about using lovable to build a presentation instead of slides, that's definitely on my list of things to try. Most recently I built a feedback analysis tool that takes raw text feedback and converts it into feature requests, usability issues, and bug reports. It's crazy to me how easy it was to build with Lovable, it's super addicting I keep iterating on it.
All my product documents that I share with the team re vision are now just lovable prototypes
Great post Elena. Love the North Metric example as something Exec level that can help move the needle. In the past I'm sure our bosses would have delegated this to us to do, but its clear its all hands on the work this decade :)
I love this! I've been vibecoding using Lovable and it's been so fun. For me the primary use case is to see if the ideas that I think are so great are actually any good :) I love the uses cases you mentioned.
Let’s go 🚀🙇♂️
Very much on board with this.
I attended a product conference in October and heard a lot about Lovable. I haven’t written code in 30 years but decided to subscribe and start experimenting. I’ve built a complete vision of my product’s future and made it fully functional. Is it perfect? No. Is it changing the conversation with clients and prospects, as well as colleagues, 100%.
Elena, I didn’t even realize the connection between you and Lovable when I started. I just heard a lot about it over the course of a few days. Happy to show you or talk through the experience.
This is amazing 🚀
Love love love this
Vibecoding is the new fuel to drive the Industries
There are so many niche Lovable use cases besides prototypes! I use it to place mockups into an iPhone frame, and to create little animations - it’s wild that it’s easier to do that with code than in some kind of drag and drop design tool.
That said, these are all on the side - I’m yet to clear the hurdle of enterprise IT / legal approval for all these apps at work 😩 I’m trying but it’s slow, and I’m not sure the juice is worth the squeeze.
Vibe coding one-off tools definitely has its merits, but a lack of standardization around tooling, templates, processes, and assets has challenges as a company scales.
Awesome for prototyping a new asset or feature, but becomes annoying when everyone comes up with a net new asset every single time