Leveraging AI

202 | The Ultimate AI Showdown: Comparing Vibe Coding tools with Mark Kashef

• Isar Meitis, Mark Kashef • Season 1 • Episode 202

Share episode

👉 Fill out the listener survey - https://services.multiplai.ai/lai-survey
👉 Learn more about the AI Business Transformation Course starting May 12 — spots are limited - http://multiplai.ai/ai-course/ 

Can you build custom software without hiring a dev team or learning to code?

The short answer? Yes — if you understand Vibe Coding, the new AI-powered way to develop applications just by describing what you want in plain English.

In this jaw-dropping session, Mark Kashef — AI innovator and data scientist — shows business leaders how tools like Lovable, Replit, and Bolt are changing the rules of software development. Whether you're a tech-savvy exec or a total non-coder, this episode will unlock new possibilities for product creation, operational efficiency, and creative freedom.

Pro tip from this episode: Don't just prompt — strategize. Mark reveals how to pair AI tools with platforms like Perplexity to generate high-performing, production-ready prompts that launch serious MVPs.

In this session, you'll discover:

  • What Vibe Coding is and why it's blowing up in 2025
  • The key differences between Bolt, Lovable, and Replit — and which one is best for your needs
  • How non-developers can use AI to design, build, and deploy real apps
  • Mark's favorite prompt engineering hacks using Perplexity AI
  • How to avoid “spaghetti code” and failed builds by getting the prompt right
  • Real-world examples of fast, functional MVPs created with vibe coding
  • Insider tricks for editing UI visually and debugging smarter — not harder
  • Why these tools are the “nuclear bomb” upgrade to basic AI agents

Mark Kashef is a data scientist, software engineer, and one of the most compelling voices in the world of AI-powered app creation. With a background in software infrastructure and a gift for translating complex tech into simple workflows, Mark’s tutorials and strategies are empowering leaders to build their own tools, faster than ever.

đź“ş Watch his experiments on YouTube: Mark Kashef

Don’t forget — this is part two of the Ultimate AI Showdown. Catch part one in Episode 200, and stay tuned for part three, featuring AI image generation tools, next week!

About Leveraging AI

If you’ve enjoyed or benefited from some of the insights of this episode, leave us a five-star review on your favorite podcast platform, and let us know what you learned, found helpful, or liked most about this show!

Welcome to part two of the Ultimate AI Showdown. If for some reason you missed part one, go back to episode 200 of this podcast. We hosted Lisa Adams and she was doing the ultimate AI showdown comparing tools for doing data analysis for businesses. It's absolutely brilliant. So go back and check that out and now two part two, comparing vibe coding tools with the amazing Mark Kashef.

Isar Meitis:

our next topic today is maybe the most exciting aspect of AI development that exploded in 2025, and that is Vibe Coding. Now, those of you who don't know what Vibe coding is, and you never heard the term before, first of all, the term was coined by Andres Carpathy, who's a big name in the AI world, who's been part of the, one of the founders in OpenAI. He left OpenAI a while back, uh, but he's still, uh, followed by a lot of people. But what it actually means, it means using AI development platform and explain to it in simple English or other languages if you prefer. What is it that you want to develop and the platform will develop the thing for you. Now, when I say develop for non-developers like me, that's a pretty broad term. Well, depending on the tools you pick, it does the design, it does the development, it does the QA and solving bugs. It does the deployment. It creates an application that you can actually use. And again, not all the tools do all these things, but just like we spoke before, you can mix and match these tools to create applications that you, that you can use. Now, the cool thing about it, people like me who are not coders, who are not computer engineers, can develop applications for anything that you want. If you are a software engineer, you now have rocket fuel in your back pocket to do a lot more stuff, a lot faster now. The interesting thing here is that if you know what you're doing, you can do magic If you don't know what you're doing, this could be really, really scary. But the cool thing is if you know English, or like I said, many other languages as well would work. You can write applications that will solve either basic or complex problems in your business. But there's a wide range of tools right now that do a huge variety of things, and they each have a specific target audience in mind, and they still have. Pros and cons. And so our guest today, uh, mark Kashif comes from a background of data science. He's a data scientist, a software engineer, but he became a vibe coding ninja. He shares priceless videos on YouTube, on how to use AI tools to do really incredible stuff. A lot of it around vibe coding, but not only that, but he's definitely somebody to follow if you want to go that next step in your AI development. And he brings together both worlds one and a deep understanding of how software actually works and how data needs to be analyzed. And on the other hand, he's really, really good in explaining it to monkeys like me so I can follow and do the same stuff and develop my own applications and do some cool things with it. And so from my perspective, vibe coding is the next version of superpowers that AI gives us. After we learn how to chat and learn how to build some basic agents, now you can use it to actually build applications that you need. And why would you wanna build applications? Because every application you use today has between 20,000 to 172,000 functions when you need four, and yet you use the really complex application because that's what you have. Well, that's not the case anymore. You can create your own applications that do exactly what you do and connect exactly to the data that you need and display it in exactly the way that you want. Um. Consistently. And so you can start creating applications as of today. And we're gonna do this with the amazing help of the amazing Mark Cashew. And so Mark, welcome to leveraging ai.

Mark Kashef:

Thank you so much. That's a very humbling intro. The bar's way too high for where I axia, so I appreciate it. Um, I,

Isar Meitis:

I, that was underplaying it. Like I, I, uh, what you do is really amazing, so I appreciate you. I appreciate it. Right on. Should I share my screen? Yeah, let's, let's get started. That's why we're here.

Mark Kashef:

Alright, cool. So, hey everyone, I'm gonna walk through three main tools right now when it comes to vibe coding. There are, if you look it up, probably now a hundred copycats of these tools, but these are three of the most powerful ones. And this basically builds on top of what Lisa just showed in the last segment. So she showed. At the language model level, like at Gemini's level, at Claude's level, how to build these applications. These are basically what we call a vertical agent that's on top of those models. What that means in plain English is bolt lovable and replicate here in order they've all built infrastructure on top of these language models and try to give as many tips and tricks and guides behind the scenes to make these into junior software engineers. And that's why you can vibe code with these in a lot more powerful way than you can with just Claude or Gemini or anything else because they have focused on marrying software engineering principles and infrastructure with language models. And just to give a, a visual, instead of just using, um, nerd speak, if I had to give you a visual of what this looks like, imagine you have lovable bolt and rept and behind the scenes, behind the curtains, you have the real star working away, which is Claude. And for most of them, similar to what Lisa mentioned, Claude is one of the best, if not the best, right now at writing code, especially production level code for software engineering. So behind the scenes, this is all powered by a brain, and right now all of them are using Claude four, which is the latest and greatest version of Claude. If I were to give you a quick comparison before we actually go into and see how they work and how they operate and the types of apps they can make in literally minutes. This is a quick comparison. So Bolt is really good at being fast and speedy, and the actual code it writes is pretty well thought out. Lovable is the most beautiful. So if you look at the design, it wins design every single day. In terms of beauty, in terms of ease of use, it's also really easy to use as well. So if you are starting out completely from scratch, lovable is the easiest way to go from zero to idea on paper that you're really excited about Bold. You have to work a little bit more on the prompting side to get there, but Repli is one of the most robust, so imagine rep lit as having a. Its own repository of tools at its disposal. They're all rep's infrastructure. What that means in plain English is Repla actually used to be like a cloud provider before, but now they've kind of built on top of their database tools, their server tools. So repli can not only build apps for you, but it can natively integrate databases, everything without you having to worry about going the next step and learning new tools to connect to these other providers. So Rep is one of the most robust, but it also takes sometimes four business days to finish, and I'm exaggerating, but from the time you send out a prompt, it could be 15 to 20 minutes before you actually get your first iteration. So if you're less inclined to know what you're doing or how to prompt, you'll get a way faster feedback loop with bold and lovable and really get your skills upskilled. Once you're ready, you can graduate to try to work with Rep Lit, because then you'll be able to plan out your prompts a lot more effectively and have that quicker feedback loop you're looking for. And then this is the last start all show before we actually go into the platforms and show you what I'm actually talking about. So in terms of MVPs, which stands for minimum viable projects or prototypes rather, um, bolt and Lovable are exceptional for you being in the middle of a meeting. Most of the times when I'm speaking with clients, you we're trying to visualize what their dream outcome looks like. I will use lovable on the side. I'll take the transcript of my fireflies, dump it into lovable and say, try to visualize what this client's actually looking for. And I'll have that run on the side while we're having the conversation and then I'll be able to show it and say, is this kind of what you're thinking? So the power of being able to use that speed is very impactful and similar to what Isar mentioned you, you wanna know when it's time to bring a knife to a gunfight and when to bring a nuclear bomb to a gunfight. And it really depends on which type of tool you want to use. So if you wanna build something highly robust in a quick amount of time, rep's probably the best way. If you want to build just something quick, a mockup to get the ideas flowing, lovable is a great option. So without further ado, let's actually take a quick preview of what these tools look like when you log in and then I'll show you some apps already built out, and I ran it ahead of time just for time's sake. But for Bolt, right now, this is what it looks like. You'll notice all of them have a big glaring text box in the middle of the screen where you can ask away your dreams in terms of what you're looking for. You can attach an image by the way to all of them and say, here's a website I really like, or, here's a design I really like. I think you can paste up to four to five images, send it with a prompt and say, try to recreate this to the best of your ability. And then one key feature here is this button. If I say something really poor, like build me an app to automate my manufacturing business with a surveillance dashboard, I'm gonna misspell it on purpose. You can see here they, they have, it's something called enhanced prompt. So if you're getting started, this will take your very vague prompt and make it more production level ready. So this will also help you become a prompt engineer in a very compressed short amount of time, because you'll start reading and understanding the flow, how it expects to be spoken to. Now, is this perfect? No. And I'm gonna leave as a little teaser at the very end here. I'm gonna show you how you can use perplexity to make you a prompt engineering deity without actually learning the fundamentals yourself. But until then, you, you would just send this and then it would actually pop up the first response.

Isar Meitis:

One more thing just to add. Yeah, go ahead. One short thing. Yeah. Uh, because you said about attaching files, what I do every time is I have like a brand guidelines, fancy PDFI upload that and then it knows how to grab my logo, my colors, my font and everything. And it, you don't even have to say anything. You literally just upload it there and then it figures out what to do with it. And it works on all the different applications in a, in a very solid way.

Mark Kashef:

Exactly. Yeah. No, that's great. Add-in. Thank you. And on the lovable side, same thing. You can upload files, uh, in terms of images as well. Um, you can connect the whole workspace. You can connect to something called super base. This is basically a database that a lot of SaaS platforms use to store data, but also enable functionality, which I'll get to shortly. And this one's pretty straightforward. You send the, the prompt as well and you'll get some form of user interface. And the last one is rept, where this one's a slightly different. So Rept on the left hand side here, you can actually click on this and you can select exactly what kind of platform you're trying to optimize for. So if you wanna build a modern web app, you can just click this and it will know behind the scene. It'll get a cheat sheet injected behind the scene that that's exactly what you're going for versus having to guess. If you wanna just pick auto based on what you write in natural language, it will guess what you're trying to build. This is the only one that I'll try to run live, just to show you how it's different from the others. So if I use a, the prompt we just made in Bolt. Okay. And you run it here, like I said, this will take. A while to get to the point where the interface is there. But one thing it's exceptional at is it plans out loud and it plans a prototype before it even builds the prototype. So it tells you basically, this is kind of what I'm thinking. This looks like, is this kind of where we're at? Or should I pivot my thinking before I even build the first version? And the reason why it's so thoughtful, you can see right here it's now building a visual preview of a prototype of my prototype to see if we're in the right direction. It's giving you a list of all the items. It's planning on adding as features. And what's also cool is even if you didn't come up with a feature yourself, it tries to suggest features that could be richer. So rep is, like I said, can be a much richer experience overall. And then it always asks for your permission, which I love. I feel like an actual boss to a junior software engineer where you have to AP approve and start the project in order for it to actually go and build it out. And once this finishes running, we should get some form of interface here that will display. You'll see right now production dashboard, there's something loading here. It's building these components as we speak right in front of me. There we go. We got some modals here. And by the end of this I can say like, this looks kind of boring, or I wish it was something else. Yep. Once I click a proven start, then it'll be on its way. It'll probably take around 10 to 15 minutes because one thing rep likes to do is it tries to make everything functional, not just build a mockup. It tries to actually make the database work. It tries to pop up a modal that says you says you wanna use OpenAI. Great. Go get me your API key. You wanna use stripe? Go get your stripe key. So it's very comprehensive in its responses. So that's what I wanted to show as a preview before we actually look at apps. Now I'm gonna show you the prompt that I've used. I'm going to show you two sets of apps. This prompt is eight pages. Is it because I'm so inherently gifted and smart and intelligent that I wrote an eight page prompt? No, I actually dictated a very small brain dump to perplexity, and I gave it a prompt that I'll show you shortly, and it helped me build a very comprehensive prompt. And the crux of the prompt is build a comprehensive AI powered IT operations command center that combines real-time infrastructure monitoring, cybersecurity thread detection, and gamified collaboration in a modern interactive web app. And then it goes through a bunch of requirements here that again, I would love to take credit for, but all of these eight pages of requirements and designs I just approved by going back and forth with perplexity. So I took this exact prompt and I threw it into each platform to give you a sense of how it would look in different platforms. So Numera Uno Bolt, I purposely just showed the code instead of the, the web app in Bolt. It took around probably, uh, five minutes or six minutes and we came up with this, which is actually pretty beautiful. It's responsive. Um, it has pretty much all the elements I asked for. You can notice here that this part looks really similar to what we, we just saw in Rept. There's a reason for that. A lot of these vibe coding apps use certain what are called libraries like, like a normal library you think of, but let's say in the coding world where you have a series of frameworks or where all of these platforms like to get icons from to create, populate these icons here. And it put together not only one tab, but if you click on multiple tabs, you'll see here security center, you have security alerts. Obviously this is all fictitional data that you can make production data, but it starts out also drafting out what the profile would look like, et cetera. And this is only one shot. Now with Vibe coding, I like to say that you're only as good as your last prompt. So the most important thing when you Vibe code is you'll notice this is my very first prompt. Is every prompt I send to these platforms the same, no. The first prompt for any of these platforms is kind of like building a house. So if you had a construction team working for you and you told them the blueprint of the house, right? If you don't tell them at the beginning that you want a pool in the middle of the courtyard of your house and they start planning the building, the house, going back later, halfway through the app and telling them, oh, I want a pool. Even though there's already two rooms there in a kitchen and the plumbing's already been put out, that that becomes a tricky problem to go through. So if you don't want to pivot halfway and now you have to do a change order like you would in real life, and they have to go scrap a bunch of code, you start getting what's called spaghetti code, where now you have all these types of codes on top of each other, and you go into this endless loop where you're not accomplishing what you're looking for, you're getting constant errors. And if you're not as tech savvy, you can't even read those errors and you keep clicking, try fix, praying that it knows what to do, and then you eventually say, this vibe coding stuff sucks. Bye to prevent that from happening, you wanna be as thoughtful as possible before you even kick off your journey. And then the likelihood there'll be more accurate will be much higher. So that was both.

Isar Meitis:

So to pause it just for one second and connect what you said before about perplexity, I do the same thing. I have a project in Claude, which is I did a lot of research on what needs to go into product design, and then I add. That as the input into that thing. And then what I do is say, okay, this is my idea. I want you to ask me multiple questions to punch holes and, and figure out the details because I don't know the details. The other thing is it has all the things you need to think about when you design a software like the user interface. Does it need to be mobile or not mobile, like all you got, all the gazillion other things that you want to be able to do. And then it has just asks me all these questions. Now, some of them I don't know and I said, well, I don't know. What do you suggest? And then it makes a suggestion and I can pick from it suggestions. But think about the AI as your software design assistant that most likely knows about software design. Way more than you do, even if you're a software engineer like Mark. Definitely if you're somebody like me now, I have the benefit. I ran software companies for almost 20 years, so I understand. I don't write code, but I understand how software is built and how it works. But if you don't, it's still fine. You can still have that conversation back and forth. And only after I have a long conversation and then I have a very solid prompt, again, like Mark said, explaining that needs to be a pool in the middle of the courtyard. Then I go into one of the tools and actually let it run and the results are significantly a faster be better. And see, like Mark said, for people like me, significantly less frustrating because I don't know how to fix it. And I'll say one more thing about the whole getting stuck in the loop of not being able to fix. When you're doing this five or six times and it doesn't solve the problem, just ask it to go in a different path.'cause you're ch you don't understand how the code runs. You say, you know what, forget it. Let's start this component from the beginning. Yes. And then just that part starts scratch. Instead of trying to fix 15 different things, your chances of getting it done is significantly higher.

Mark Kashef:

Yep. Exactly. No, that was amazing.

Isar Meitis:

You know, one, one last thing, sorry. Uh, most of these tools have like an assistant that doesn't actually write code that you can just say, okay, let's brainstorm this for a minute. Uh, inside the tool itself, right? I do this in replicate all the time and then it doesn't write code. It just helps you kinda like troubleshoot and come up with new ideas on how to solve the problem. And then you go back and try to edit.

Mark Kashef:

Yeah, you stole my thunder. Yeah, I was gonna show that next. So, um, oh, awesome. Perfect. No, you're good. So, um, I was just gonna show the app first in lovable and then repla and then show that functionality. So in lovable, that exact same prompt I showed you, if I put this back, you'll see visually, although it's somewhat similar to what I just showed you, it is ever so slightly prettier. It, it focuses on the little things like the size of the font. You'll notice bolt here, it kind of put a lot on one screen and I have a bit of overload, cognitive overload when I take a look at it. So even though this is pretty, there's a lot of going, there's a lot going on. There's titles, there's subtitles, there's headers. So lovable is very lovable in terms of the designs it creates. And as you go from tab to tab, you'll just notice that it's very easy on the eyes. Uh, lemme see. This one works. At least see this one. Um, and you'll see by the way, if, if there's an error in the code, you'll always see this popup that says, try to fix. So either you can look at the logs if you're a nerd like me, or you can click on try to fix, and it will try to figure out what is happening in the underlying code. And then last but not least, this is what Repla put together. So repla, I will say, will always be slightly less pretty than both those platforms. But in terms of functionality, you'll see like it jumps ahead, it asks permission. It's asking me right now, how does the application look and feel to you? Are all the features working as expected? So it's literally waiting for my feedback to tell it, yeah, you did a good job or not a good job. The other ones are kinda like, here, take it. Uh, here's my report. Uh, lemme know if you like it. If we go back to what Azar was mentioning, all of these tools have something that's called chat mode. In chat mode, I can actually ask a question like, what do you think we should add next? Okay. And then instead of actually executing and writing code and. Making the application more bloated. It just talks to me. I'm talking to Claude now, but I'm talking to Claude in the context of my project. So if it comes up with an idea or a plan, I can read through it. If it looks logical, all I have to do is click on implement this plan right here and then now it will go and execute it. But at least now we're on the same page. I noticed that a lot of times that I will spend 70% of my time even in lovable right here. It'll be called uh, chat right here. If you click on chat mode, I'll spend 70% of my time here. I'm only 30% of my time actually writing the code.'cause I'll spend five 10 messages to make sure we are 100% on the same page before we go and write the thing or do the thing. And then rep has, uh, the same thing as well. And then rep's just really good at dealing with feedback in general. All of these have also, uh, visual editors. So if I go to here, um, I can click on this button right here and then I can go select a specific element. And you'll notice on the left hand side, it's now referring to this exact element. So instead of. Praying that I send the prompt and it knows exactly what I'm talking about. I can say, no, this one, this is what I wanna change. Same thing with, uh, lovable. You can click on visual edit and I can say, this button, this button's ugly. And I don't even have to send a prompt. Sometimes if I wanna just, um, change the size, I could just do it here without a prompt. And that's how a lot of these platforms differ ever so slightly. You can't do this exact functionality in Bolt, but in lovable, you're allowed to be specific. I can even, by the way, Google a specific font name, paste it here, click save, and it will make the change in the code, which is very powerful because it saves you from having to guess how to tell it the thing in natural language. And then in terms of rept, I don't think there's, uh, is there a prompt helper? I don't recall that, um, myself. But at the very beginning, you can get some help going back and forth on flushing out the prompt. And one thing I just wanna show you on that rept, again, small nuance is you'll notice it actually takes physical screenshots of the web application while it's processing, whereas the other ones are solely depending on code. So where I say it's more robust is it's not just looking at its code, it also is taking screenshots. Like I would send to OpenAI or Claude and saying, analyze and see what's wrong. Let's see, before the user catches it, let's catch it ourselves. And what I mentioned before in terms of being more robust, you can notice here if I go on. Uh, database deployments, all this stuff. I go to all tools. All of these tools are pre-built in rept. So if you want a database, if you want the ability to use Google Sign in very easily, all that's built into what's called rept authentication. They've kind of made one whole ecosystem of tools. If I go back to Bolt and Lovable, if I want to enable something like Google Sign in, I'm gonna have to go to something like integrations here. And then I'm gonna have to create what's called a superb base account, which is like a database account. And I'm gonna have to connect to that superb base account, then give it some credentials, then it can start to build functions that allow me to do authentication. So that's just one small microcosm of using these tools, the differences. These can get me a prototype immediately without me having to think about anything in depth. Rept will allow me to go much deeper. And what another cool thing about Rept is they have a mobile app. So if you're on, uh, the bus, if you're on a plane, if you're waiting in the airport, I could have built this on a mobile app. And just prototyped on the go. Vibe coded while waiting for my delayed flight, and then I'd be on my way. So that's just one more idea. And the last thing is on the Repla side, I've used Repla as a developer for years to deploy applications on a server. The fact that it's all built in, again, in that one ecosystem, that means that they're really good at cloud, they have secure cloud, they're already trusted by hundreds of organizations, and now they're just marrying their whole ecosystem to cloud. So that's where I'd give Rep the edge on robustness. Now, being mindful of time, um, I'll see how much time I have left. I'll just show you the hack and perplexity. If you're looking at all this and you're like, I'm still stuck on how you wrote that prompt, I'd rather unblock that for you before we end up. So in perplexity, and you can use what, whatever language model you wish that's connected to or hooked up to, uh, a web search. So you can use, I usually use deep research, but just for time, I'm just gonna use, uh, a very quick search. And what I'll do is the following, and I'll just dictate in natural language so you can see how poor I am as a prompt engineer. So I want you to act as a prompt engineer with a specialty in product design as well. And I want you to look up all the documentation, watch YouTube videos on the platform's, lovable rept and Bolt. And I want you to come up with a universal prompt that I can create for my e-commerce business that would work for all of them. And build a beautiful minimalistic e-commerce app that lets me manage my Shopify orders programmatically in just using my natural language, typing in some form, some form of text box. And I want you to output that prompt in an un unformatted code block in mark down so I can just easily copy paste it. So in this case, in plain English, I just said go and watch YouTube videos, go and read documentation on all these apps, and it will know that it's using Claude behind the scenes. So in a way, it's also gonna research that. And when I send this, you're gonna see what's gonna do. It's gonna go through lovable documentation, it's gonna go through, uh, rapid documentation. It watched the ultimate guide on, oh, if I go back, my bad, it watched the Ultimate Guide on using, uh, repli and Bolt. So let me just try that again. Worst case I'll just do, there we go. So lemme go back to what it did. Go to sources. So I went to Reddit, uh, went to YouTube videos and watched, uh, I watched videos on. Shopify integrations. It went through gpt, it went through GitHub, which is basically a repository for different apps. And then it came up with, after doing all that this prompt, and you can see here, this exposes my lack of genius'cause it did all the hard work. Build a beautiful minimalistic e-commerce web app that connects to Shopify store and allows me to manage orders programmatically. And then it gives a list of all the different requirements, clean, modern, minimalistic UI with responsive design, and basically a laundry list of all the things we want in this app. And then you could just copy this and throw it into whatever web app builder you're looking for, and you'd be on your way. And the cool thing is, one extra pro tip I'll give you is if you get stuck, what Isar mentioned is amazing, which is trying to pivot or going to chat mode to discuss. But one other thing you could do is, I like to actually, since you have access to the code, even if you can't read the code, I like to ask it, okay, where do you, which file has this problem you're talking about? And it'll tell me this AI analytics tsx, and I'll just go copy, paste this whole thing, give it to maybe Gemini or Claude, uh, a brand new version of Claude with virgin eyes on the matter. And maybe they'll say, you know what? It's missing this. And you're like, aha, this is the problem. So the fact that you have access to code, even if you don't know how to read code, you can use it to help you get back on track if things go off the chain. So that's on the prompting side. I'm gonna pause

Isar Meitis:

This was nothing short of mind blowing, like the chop people, like this is phenomenal. This is incredible. I can't believe I did not know about this. Good. And I did a little questionnaire, like a little survey, who knows about vibe coding. And most people didn't have a clue or kind of like knew about it, but didn't. So I'm, I'm sure this is gonna take a lot of sleeping hours from people to play over the next few days, uh, which was the whole point. Uh, mark, again, this was nothing short of exceptional, uh, as expected. So I set the bar high, but you jumped like 10 feet above the bar. Thank you. So thank you so much. I appreciate it. Uh, if people wanna work with you, follow, you know, you connect with you, what are the best ways to do that?

Mark Kashef:

Sure. Yeah. So, uh, YouTube is just Mark Cash if, uh, if you wanna follow my Mad Scientist experiments. Um, otherwise, uh, prompt advisors.com if you wanna engage on a project. I just threw it in the chat there. And yeah, I mean, YouTube will give you 90% of my life, uh, and what I do and what I'm working on. So that'll be the best way to go.

This is the end of part two of the Ultimate AI Showdown. But don't worry, there's part three and four of this incredible series of the showdown. So next week we will release the next episode. That will be episode 2 0 4 of this podcast in which Rory Flynn, one of the top AI image generation professionals in the world today, will compare AI image generation tools and how to pick them and how to use them in the most effective way. And until then, have an amazing rest of your week.

People on this episode

Head Shot

Isar Meitis

Host