Subscribe
Share
Share
Embed
The WP Minute brings you news about WordPress in under 5 minutes -- every week! Follow The WP Minute for the WordPress headlines before you get lost in the headlines. Hosted by Matt Medeiros, host of The Matt Report podcast.
Eric Karkovack (00:00)
Hi everyone, and welcome to the WP Minute. I'm Eric Karkovack. Today, we're sharing a segment from our episode about Vibe coding. Stranger Studios co-founder Kim Coleman and my colleague Matt Medeiros joined me. We discussed the pros and cons of code generation and provided plenty of tips to ensure quality and maintainability. Now, you can check out the entire interview over on our WP Minute Plus channel. Visit thewpminute.com
for all the details.
Kim Coleman (00:30)
So we actually published three plugins this week, not this month, not this year, three in a week. And ⁓ I think when you're vibe coding, when you're launching things that are largely AI based, you have to use a human AI human system. So ⁓ Eric, talked about the architecture thing, the human designed and created a brief, even with the help of AI, let's say. You went back and forth.
Eric Karkovack (00:35)
Wow.
Kim Coleman (00:56)
in chat with AI to design the framework structure, functionality, no-goes, rabbit holes about a project. You handed it to AI to develop it and you got it back and you either tested it, tested it thoroughly, had the code reviewed, handed it to another AI to code review. All those things are great. At the end of the day, there has to be a human saying, how important and how critical and how bad would it be if this code is insecure or fails or breakdowns? ⁓
What am I opening my customer, my user up to? What risks am I opening them up to? And if it's relatively low and you're just like, you know what, this is a landing page about snow and has a map, there's really no risk. People hit the website. I mean, the worst thing that could happen, I have some kind of injection point that is in the server and something goes haywire and I pay some crazy Google Maps fee. I'm trying to think what the worst thing that could happen is.
So I think having a human sense of the security and the risk of it being incorrect is kind of an important thing. But also as quickly as that code was created, that's how quickly bugs can be fixed or faster because it's a day later and everything got way faster already. So we're kind of in this mindset of if it's low risk, push it, let users be the testers, let users be the stress testers, let them try it and say, I wish it did this, let them try it and say it's broken, it doesn't work this way. ⁓
It's way easier to get that kind of feedback when there's something for people to play with than it is to say, what do you want? I don't know what I want. Give me something to try. The same is true with localization for paid memberships pro. We have a localization server. We are putting AI translations out to our customer sites. The people that were contributing translations on their own, zero. The people that are fixing translations that AI created, 100%.
they're like, ⁓ it's easier to just fix this translation string than it is to start from scratch. They will take a 99 % complete translation with fuzzy strings and get it to 100%. They won't do it from zero to 100. So I think giving them a little bit of slop is useful.
Matt Medeiros (03:10)
useful slop. You know, there's something I want to. There's something I want to add, because I like. I mean, obviously, we're all trying to root for the human side of this stuff right now to save our jobs and make sure that we still have a purpose in like the careers that we have now or not. Things could change. don't know. But, you know, I think what I'm trying to get to now is do I need.
Eric Karkovack (03:10)
That's a really good point.
Kim Coleman (03:12)
Useful Slop. Use my Slop and I'll make it better.
Matt Medeiros (03:39)
Like, because I can build the thing now, do I really need to build this thing? Like, does it need to exist is like the first question that I have to ask myself because I will literally just keep opening up Cloud Code sessions and just creating stuff. And it's not a healthy space to be in because I can't even remember like what I started sometimes. Like, where did I leave off on this particular project? ⁓
But I think for the business side of things, especially for like Paid Memberships Pro, you probably have customers that come to you and say, I made this add-on with Cloud Code, it's not working, can you help support this? I think our abilities as business owners now might be to quickly launch these features that otherwise might never even reach the product. It certainly might take months because you're just like, it's not a high priority.
But you can now kind of like get out in front with the caveat of like, this is like, these are add-ons from the beta program. And of course, if you're gonna use the beta program, it's not gonna come with support, but we built a bunch of these things for you, go use it. And hopefully that's a stopgap for that end user to then look at that and go, all right, I was gonna build it, but I see that they have it, right? And if, you know, I don't know what the perfect balance is, but I think there's a way for product companies to
to get this stuff out faster. know, again, it might not be supported in the core product, but at least you have it. And maybe the customer wants to go and fork it and do something else, that's fine. But like, you're leading the pack because what'll happen is you'll have the people who start to complain about whatever, features lacking or this thing should be in paid memberships pro, I can do it faster, blah, blah, blah. I actually saw this on a Gravity Forums webinar yesterday where somebody was like, well, I could do this with AI and it's like.
Good luck, like you can do it. But we're not going to support it. So you have to use our official channels. I don't know how the dust settles, but I think like shipping a bunch of stuff is still smart. ⁓ And it's only going to hopefully benefit because you're the brand holder, right? You own the brand and people are going to get that code from you and trust you, you know, to to back it up.
Eric Karkovack (05:35)
You