The trick is that you have to be a good coder to get the most out of "vibe" coding. It works great for me, but I deploy all of the knowledge I've acquired over the decades as a professional developer. You need to know how to architect systems, what data structures and algorithms to ask for, how to design a product, many facets of graphic and user interface design, how to parcel out work, how to parallelize tasks. Even which ideas are worth pursuing is an intuition you build up over years. "Vibe" coding really is magic and I'm highly scaled, but I don't see how it could possibly work for all but the most senior developers. In some sense, it's like writing LISP macros on steroids.
I was able to teach my interns more about architectural designs instead of coding. Teaching them more about DDD instead of going through what’s broken with this function. We might be close to a point where you can teach product people about these basic concepts, packages and saas tools, and have them vibe code a whole app.
Today, I am implementing tag-triggered webhooks so they can get triggered based on the tags assigned to messages.
Use case: for example, I want to auto-tweet all my advice messages and auto-create linear tasks for `company` todos, auto-start a cursor agent when I tag messages with `Cursor task`
For some reason, I got 16 users out of nowhere, so I added a landing page last week. The connector marketplace is next, so that I can share these sub-connectors with the other users. Need a couple more weekends.