Why develop on Semantic Kernel?

- So I'm really busy as a developer. I have a deadline, and I'm feeling the pressure. I got to get it done. So Semantic Kernel, out of the box, works. You can quickly integrate it into your app. It's like that versus building the kitchen yourself. Who wants to do that? Another benefit of Semantic Kernel, which is obvious, but you have to get into it, is prompting. So I don't know if you know it, but I don't use the word prompting (laughs) very much until now, and there's so many variants on prompting. Hey, are you doing prompt engineering? Did you see chain of prompts? Oh, my gosh, there are prompt injections. So it really is being used all the time but in reality, no one is making very complex prompts because it's hard. So imagine easily making complex prompts, multifaceted prompts, prompts that do all kind of things like connect to native code. I know you like that. I know we like that. Things like that come for free with Semantic Kernel. So the third benefit doesn't feel like a benefit. You're not going to notice it. We used Raymond Loewy, the designer of a Coca-Cola bottle, and his principle of MAYA, most advanced yet acceptable. We did not make this Semantic Kernel to be like what is this? This is a whole new model. Nope, you write native code, which you're used to, and you can integrate these cool power prompting capabilities, and it's like, oh, this is advanced, but it's familiar. So Semantic Kernel has has these three benefits by design to make it easy for you to meet your deadline and be that 10-X developer because at the end of the day, this stuff is changing so fast that the last thing you want to do is just get caught in it. You want to use it in your app and get going.