GitHub Open Source Friday, 6 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Empowering Developers with Low Code Solutions - Amplication - Open Source Friday

Description

Amplication is a low code solution to building a Node.js app. If your provide the schema, Amplication can generate backend code, a REST API or GraphQL API, and Swagger documentation. You can even sync it with your GitHub Repository.

In this video, Developer Advocate at Amplication, Michael Solati gives @blackgirlbytes demonstrates how Amplication works.

0:00 - Introductions
4:33 - What is Amplication?
6:02 - Demo: Generating a Backend with Low Code
14:32 - Connecting your code to GitHub
16:42 - Generating Swagger API documentation
24:18 - Q&A
28:30 - How to contribute
31:53 - Fun Chit Chat

Join @blackgirlbytes live for Open Source Fridays at https://www.meetup.com/github/.

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

A

I'm not sure if anyone's watching yet, um but basically you're watching open source friday. um Today, I'm joined by michael celotti. I hope I'm saying your last name right um from application and application is in an open source, um low code, back-end development tool, I'll I'll. Let him explain it a little bit better than me, um but hi michael.

B

Hi, uh thank you for having me this is, I think, our second time actually being able to chat, like you mentioned earlier, which our audience didn't see our first name actually seeing each other. So this is definitely a super exciting experience.

A

Yeah, it is, I love to like, um just I don't know like put a face to the voice and and the name and everything. So this is really good. um How about um you go ahead and like introduce yourself as well like talk a little bit more about yourself um and also what is app implication.

B

Sure um so my name is michael. I am a developer advocate at application. um I've been in the world of software development for roughly the past seven years. Now I keep getting it wrong because for a while I kept saying five years and then I realized the pandemic happened. So I had to add a couple of years to that um but yeah.

B

I started as a front-end engineer after a coding, boot camp in connecticut got some good experience at dev shops and at ad agencies, and then I made the transition into developer relations, which I've been doing for now. This one I can do the math for nine three, no four, four.

A

Years now, yeah, that's impressive. Yeah.

B

No, it's it's! It's probably one of the best experiences. Okay, if you're a software developer, I'm not telling you that your job isn't rewarding in any way whatsoever. I'm just saying one of the highlights of being a developer advocate is the opportunity to go to meetups when they're happening and actually meet you developers and talk to you and learn about like what you are doing and figuring out. If there's ways that uh we can help, you build better stuff.

B

um I think in our previous conversation I I mentioned that I'm not going to make something that's going to change the world, but I love supporting developers that are going to be able to create that next amazing thing, and so for me, that's one of the highlights of being in developer relations is helping developers build amazing things.

A

Yes, I I love the way you put that I think there's like two types of software engineers in the world, the ones that like to build amazing things and the ones that like to support people building amazing things. I think we're the ones that like to support them. Yeah.

B

It's it's, it's really rewarding, and sometimes it's not just um the developers are building the next big thing, but sometimes it's someone just getting started. Building an application. There's a um this is just a completely random rap. But since it's open source friday, I feel comfortable uh making this little diversion. But I maintain a uh an open source project. um That's based around making geo queries um and every once in a while. I like to look at on github yay talking about github.

B

uh I can see what public repositories are using my npm package that I publish um and then you end up being really surprised at how people are using your code. um One of my favorite things, I've seen is there's this application. That's um helping people pair with dogs and cats that are in animal shelters based on location.

A

B

That's nice. I wasn't gonna make that, but I love that this exists, and I know that I'm supporting that in some sort of way, and so that's like one example um not related to anything we're discussing.

A

You enabled that, though, you enabled that that's awesome.

B

That developer did the hard work, but I feel like I have at least like a one percent claim to being able to make that happen.

A

I mean geo queries, I don't know. Maybe it's cause. I've never done something like that, but it sounds. It sounds complicated to me, so you did some more work too, but yeah. That's so awesome to hear um so you introduced yourself uh what about what is app implication. I know we talked about it on the twitter space, but maybe people that were on the twitter space.

A

I mean on in this twitch stream weren't on that twitter space. So I would love for like a little bit of an overview. Of course,.

B

um Application is a it's a tool that enables developers to build back ends that are they're quality, node applications. They are built with, like authentication and security in mind, they're, very scalable, they're extensible.

B

So, whatever code that's generated for the back end, if it doesn't quite work for you, that's fine, you can completely uh modify it or change or hook into the code wherever you want, because, unlike some back-ends as a service, where it's kind of just a black box like yes, you can put things in and yes, you can pull things out, but getting inside the box and mucking with the code isn't really an option.

B

We're not that. So we want to give you a lot of the benefits that you might get with services like uh aws, amplify or uh firebase, um but we want to give you a little bit more. We actually want to give you complete control over that experience, so yeah a tool for generating scalable, secure quality, node applications with uh providing you api and rest api endpoints and a graphql endpoint to do anything and everything that you need.

A

That sounds awesome that sounds very, very cool um and I'm still having a hard time imagining how that's possible. So, if you're ready for a demo, I'm happy to to see that.

B

So here is application.com, um so we're gonna get started with logging in we will log in and we'll log in with our github account.

B

This should only take a second all right, so we're introduced to our dashboard, where we can see our different applications. um I'm actually gonna switch to this, like demo, workspace that I have here and I'm gonna get started with creating a new application, so we're gonna start our application from scratch, um and this is this is kind of maybe a little boring for some people, but we're gonna just make the basic to-do list application.

B

So what does a to-do list need to have? um You need to be able to handle user accounts because different users are going to end up using the to-do list application and you also need what is it um to do's so list the to-do's to do well by default? Application starts with creating a user collection or entity which this is a table in a postgres database. That's automatically created for you. It has all the fields that you might possibly need and you can always add fields to it. So for user authentication that's good to go.

B

We don't need to worry about that, but the next thing that we might want to do is: uh let's create something to do our to-do zone so we'll create a table called tasks we'll create that um and what sort of things will a task need? Well, I know that a task needs to know that if it's been completed so I can add a field called complete it close enough. I might have spelled something wrong.

A

We get it completed.

B

uh Knowing if the task is complete enough, that should be required so we'll set that required and because this is a like, it's either completed or not. That's kind.

A

Of a bullying statement yeah so.

B

I can choose to set this as a boolean field. Awesome and probably the only other thing that only other things. Our tasks need is the actual task itself, so I will create a field and I'll just call it text and that'll be the text field for the task. Yeah it'll be a required field and the last last thing we need is to know um who this task belongs to so I'll create a field called user, and this is how I'll be able to identify tasks to users.

B

So we have our user field. This is going to be required, and over here automatically, you can see that, based on the name user that we're assuming that this isn't a boolean, this isn't a string. This is going to be a relation to a different entity or a relation to a different uh table that we have and so we're associating that to the user table automatically, and so in this case one task can be related to one user. That makes perfect sense, given the context of what we're trying to do.

A

So application just has that intelligence built in that. If you create a user field, it's going to connect it to that user table that already exists.

B

Yes, absolutely.

A

That's impressive: okay,.

B

And so what you'll also see, um I'm so excited you're excited about that. What you'll.

A

B

Is going back to our uh our entities or tables I'll I'll use tables for now, because I think that's probably understood by most people, if I click on user, I can see that a new field has been added called tasks.

B

If I click on tasks, I can see that a user can have many tasks, so it automatically creates the relation between them, as you would expect it now.

B

Theoretically, if we lived in a world where it should only be one user, one task, we can always toggle that field and let's say if, in reality, uh I'm going to switch that back, because that's a horrible idea, let's say in reality, um use the user field and task is going to be related to something else. You could always change whatever entity, you're uh or table. You want to relate that to so you're, not locked in by the naming convention. You can just swap it.

B

However, you want we're just making a educated guess as to what you're looking for okay. So um I mentioned that we also take into account like security and making sure certain things are um not. Everyone should have access to every bit of data. Like that.

A

B

Sense, I think.

A

B

So I'm gonna go back to our tables entities, I'm gonna click on tasks and over here we have this area called permissions. If I click on it, I can see um the different like for the different crud commands. I can enable and disable them based on who I want to have access to so right now viewing tasks, creating tasks, updating all of them are anyone is able to do it. But if I don't want people to be able to delete tasks, I can disable delete tasks.

A

Oh gotcha, and what do we mean by public and granular.

B

So um conceptually we have something called okay up. First, we have public public, allows anyone uh to access this api endpoint. It is a unsecured api endpoint at this point, granular lets me pick. Oh gotcha. Actually uh this this might sound. Okay, so there's a concept called access, control lists uh which I think is common in backend development.

B

I am not a back-end developer, I'm a front-end developer by trade, but I'm familiar with the term of acls, and the idea of that is different. Types of users should have different type of access to data, and so users are put on these access control lists, which we define them as roles. So you might have users, you might have admins and stuff like that, so I can granular.

B

I can say that users should have permission to the completif field and that's it or so that's our granular, where we can define what fields uh users should have access to, um and then we have our roles, which is like all roles, have access to everything.

A

Gotcha, okay, that makes a lot of sense.

B

Sipping, coffee, sorry, so once we have all that done and set in place, we can actually um commit these changes in application. So I'll just do init commit make changes and build. uh So this is generating a new build. This will take maybe 10 20 seconds.

A

Okay, so far, I really like how um easy it is to navigate and understand what you're doing like even where it showed the like tasks are one to many versus um one to one or whatever, like that relation, I think, is good for people who may not have like a real understanding or or really a lot of experience, building out um like relational databases and stuff like that. But that's that's just my one observation.

B

No you're you're absolutely right. I think it's an awesome thing. um So if the the we've committed the changes that we've made to our backend, so we can click on view code and we can see that we have our server that's been generated for us and we can click onto here's. Our task I'll do uh task controller base file, and this is the this- is the file that's generated for our tasks.

B

uh We can see that we have our crate task, which you can see like all of these things that are added to it, but they're all kind of necessary things, especially if you're building a secured back end. So here we're saying yes, uh we're gonna verify the user using the acl, um checking the access control list, um we're saying what users can access the data we're seeing that?

B

Yes, this create function is going to be from a post request where defining the data type being returned is going to be a task data type um and then we're doing the creating of the.

A

This is right here, easy wow, yeah.

B

So you can, you can download this code and run it locally right away, but like I because we're all about you having code ownership but like in the real world, chances are you're not just going to download code off of a website. Chances are you're working on github, so we connect with github, so I'll click connect with github and if I don't have a repository which right now this this org does. My github org does not have any repositories. Okay, I'll just create a repository I'll call.

B

This uh osf open source fridays create the repository um and let's look at it, and so this created a blank repo on github. um Let's get all this code into github right now, so I'll just click rebuild just so you guys can see what this actually looks like.

A

This is no I'm my mind is blown that just by you um um kind of just doing, building out how you want the schema of your database to look it's generating all these different files and then I've seen swagger in there. So it also generates like api documentation for you or.

B

A

B

I will show you, I will show you more in a second um sorry, there's a lot and I know there's only so much time so I'm going to try that's.

A

Okay, how to keep it together.

B

So this is our initial commit um that was created by application. It opened a pull request against github and we can see like some of those files that I showed in the code viewer on application. These are all here. I am just scrolling through it really fast, but you see just so. You know like it's creating the endpoints for users, it's creating the endpoints for a task. It's doing this data validations when you write data. uh It has so many of these things that are here like oh here's.

B

Well, I guess it's technically not an interface, but here's our here's, the type for when you're going to query a user like these.

B

All these things are generated for you automatically, and so, let's just uh sorry, I had to scroll all the way to the top, because there's just too many files, and so let's merge the full request and okay, we've added our code base right to github and we can work off of github and so just a couple more things on the application website that I want to showcase real quick, especially because you mentioned the swagger stuff is. If you go into your settings, let's go: where is the apis.

A

B

So, like I mentioned, we generate a graphql endpoint. If you don't want graphql, you can turn it off. uh We generate uh rest api endpoints that are self-documented with swagger. If you don't want it, you can turn it off. um I don't think this will do a lot of work with both graphql and wrestling.

A

B

You can do that and we also generate an admin ui which is kind of like a easy way to just jump into the data and modify it, and you can enable that and disable that as you want. So I'm showcasing all this because I actually have a little application.

B

I just want to showcase real quick, okay, see how well this works.

B

It also, let me showcase the um the admin panel and stuff like that, that we had mentioned cool.

B

Okay, so this is a basic application that we have created. That's designed to showcase excuse me showcase different restaurants, um so I have a ton of different restaurants. Here I can filter by different cuisines, so I have: let's filter buy american food.

B

I can click onto any of these. Restaurants read some information and you can leave a review on this and I'm showcasing all this, because this is actually hooked up to a application project that I have, and so this is the admin panel that I kind of mentioned before, where I can see here's my users, which uh there's two users, here's all those restaurants that I had before uh the different cuisines that I had filtered and reviews that people can leave so like these are all different fields and all different tables I created in this project.

B

So this is kind of a more complete project and just to show like this is really kind of working locally. I'm going to leave a review on this one. Two one falten I'll, say food submit that that reviews over.

A

B

And if I go into the reviews in the admin panel give this a refresh there, we go. Here's our one, two one fulton review great food and the admin panel is really cool. Sorry, I'm rambling. I really.

A

No, I'm I'm I'm into this.

B

We discussed relations well. Reviews belong to restaurants. A restaurant can have many reviews. So when we're looking at this review in our admin panel, you might notice that the restaurant has a link. You can click on the restaurant. Here's all this restaurant data and, let's say 121 fulton street- is now 121 fulton avenue. I know crazy, wouldn't happen, um save that that should be updated, and so, when we refresh this here.

A

It'll be reflected.

B

It won't be reflected apparently.

A

No, it I see it it's um it's in the alex. Yes,.

B

I changed the address, not the name: okay, okay, my thank you for the catch, though um anyway, so yeah this. This is a simple-ish uh project. I have, I actually spent more time populating this uh application with data than I did with actually building the back end wow. But if you were a developer- and let's say let's say you were working at yelp- that's why I have it. This called the amp, um it's yelp application. Let's say you were working at yap and all of a sudden, your uh the higher-ups are like okay.

B

This is all cool and dandy, but why can't we call this restaurant where's, the restaurant's phone number like how? How long would it take to add that phone number field forever.

B

In so many different possible places, so let's do this with application, I'm going to find my yamp here's my amp. Let's go to our entities, let's go to our restaurant and here's all the fields that a restaurant has. So, let's just add a phone number field.

B

um I definitely know not. Every restaurant has a phone number, so this isn't going to be a required field, but this should all be good single line of text. um Let's commit to changes and build.

A

Wow- and it doesn't, I feel like whenever I try to this- could be just me not being a good at back-end development, but whenever I've tried to add new columns and stuff like that, it really messes up the whole schema, and so this doesn't do that.

B

It will not be a concern um everything is handled or generated by us and we're writing the code. For you, though, you might want to read the readmes we generate, but other than that you should be good. So, let's open up github. So this created a pull request with this new um new telephone number field. And if I go to files change, I can see. 19 files have been changed, so here's my uh interface or type for the restaurants.

B

uh It has a new field called phone number, which is either going to be string or null um and then there's interfaces for like when you do a query to create a restaurant or a query to sort restaurants.

B

They all now have this phone number field and you can see a phone number is added in all these places, where you as a developer may have had to remember, to add it all, which would be a pain in the butt, but we're handling all that for you automatically, um which I think makes this a really compelling experience because making changes now.

B

Even if it's just one field, you can do it in like five seconds and we've updated, 20 different files for you and again you haven't lost scalability, you haven't lost security, you haven't lost anything. The only thing you've lost is an excuse to your supervisor. Saying hey it's taking time to do like that's. The only thing you've lost excuses.

A

Yeah cause they're, like it shouldn't, take long, I'm about to, like you know, as a developer advocate. Sometimes you have to make like a quick demo or something I'm about to start using application. Now that you showed me to just like spin up a quick back end and then like do the front end hold the front end on top of it.

B

Absolutely, and like I I know um in in past experiences, I've developed applications with other back end of this service providers for demos to work out real quick, but in the real world, like oftentimes developers, are working with traditional rest, api, endpoints or graphql backend, as a service providers, sometimes use sdks to simplify the process. But that's not a typical experience, especially in a enterprise environment where some developers might be aspiring to go to uh with this we're. Providing that same ease of use of building a um a back end.

B

But for something that can is enterprise-ready is designed to be used in the enterprise world. So you're getting the best of both worlds, you're getting a enterprise quality tool and back end with the ease and simplicity of any like headless, cms or back end as a service product.

A

That's awesome, that's awesome. Do you mind if I um check some of the comments, because I did see a few questions coming out? Maybe one or two, um um let me just put it on the screen. Basically pomeranis.

A

I'm sorry again, if I said your username wrong, but they said if you want to change a behavior, do you add a new file that overrides behavior and what happens if you change the underlying app in terms of adjusting your code so.

B

I'm gonna, I'm gonna, make some assumptions here that, like let's say when a user creates a task, so we have our crate task. um End point that you want to auto. Let's say: hypothetically, you want to automatically make a task uh false right, like you want to hook into the data before it's written or something like that and just modify it, um and you can do that. So I I showed I think I showed somewhere earlier where our task endpoint was, and if you just wrote code inside of there awesome.

B

That's that's all that you need in order to make it to work, and then, when you make the changes on application and we send the pull request to github typically, we should not overwrite it because we're using git diff to make the comparisons. And so we want to keep your code in place. um There might come a point where you might run into some conflict with code.

B

We generate in the code that you have, but again just like rebasing or updating the branch that you're working on you can just address the git diff on your own. However, we are working on a two-way bi-directional sync, with github such that we will keep your code like. We will keep our version of the application project up to date, based on your code that way, the next time we generate it, we're not get necessarily get diffing on github we're already taking that into account.

B

While we generate the code, um so typically, you should be fine, because git diff is a thing, but we're working on ways to make that experience better as well.

A

Perfect. Thank you thanks for that question petros and thanks for um uh correcting me on how to say your name or giving me easier method actually lazar said. Is there support, for. I never know how to say this, but it's basically the thing for language, translation.

B

Yeah the pronunciation is as simple as you would think. I ate man if I'm wrong, I'm not acknowledging that.

B

um uh For support for i18n.

B

No okay but we're building api endpoints, I don't know well, I guess you might want it with swagger. The answer presently is no, however, we're working on a system for allowing plug-ins. So when we generate the code for you, you can hook in and make the modifications or add features to the code base. So, theoretically, while it doesn't exist now, that's a feature that um once we have plug-in support that our uh developers can create plug-ins in order to add that functionality.

A

Perfect um and now I learned how to say it.

B

So if you guys want to get started with contributing to application, you can go to application.com at the very top you'll see it says: application is open source, so click on that and that'll take you to our application repository.

B

If you wanted to you, could just like clone the code locally run it and you'll get the same exact experience as you did on the website that I demoed earlier uh application is a free and open source tool. We will always have a we'll always be working in the open source and working the public for anyone and everyone to see.

B

So, if you don't want to run on the website, you can run it locally. That's how you get to it. We have tons of different issues that are available for users if they want to contribute. If you have issues you can report them, we also run campaigns from time to time. I say time to time it's kind of like a regular thing.

B

I think we've ran two or three of them this year so far that are like our blank issues for first timers, where um we have a list of issues that we think would be uh good issues for people who are new to contributing to open source projects to uh as like their their first project sort of thing, um and usually for some of these, we offer some sort of swag, such as like t-shirts sticker packs um just to like get developers feeling comfortable uh working in the public, working open source, contributing to public repositories and stuff like that so yeah, um and if you want to, if you don't feel comfortable quite yet uh getting straight into contributing code um still visit, application.com uh and feel free to join our discord.

B

Our discord community is sorry.

A

It's really good discord, though, like yeah.

B

Our discrete community is pretty active when it comes to like discussing um like just anything and everything like right. Here we have like this conversation about data structures and algorithms. We have members of the team discussing things we support uh bugs and issues that people are taking. We take it like feature suggestions here. We have a ton of things going on in our discord, so if you're not ready to contribute code, but you still just want to get involved with uh application in our community join our discord.

A

B

Sound like the command, I'm sorry.

A

No do it now, I'm kidding petros has another question that said what happens when your um your core code, I guess, is the application generated core cord- has a new version. Is it silently incorporated through the next build, or is there a separate way to do the update.

B

um So I'm assuming what you're referring to and I'm going to answer it as such, is that let's say you build a application with application version. 0.13 we've rolled out 0.14 and now you want to build an app now you make an update to your application using 0.14 and what happens so diff versions. What happens? Oh okay, you said yes exactly. I actually experienced that earlier today. Oh my god, I don't know if I can actually show this, because I don't know if it will be here.

B

Is this it okay? So this is an example of that, where the gamp application, the game application, um was built with an older version of application um and without making any changes to the code. I just clicked create, build or commit build and it automatically created the pull request and provided all the updated files and it also modified the files that needed to be updated, because these were differences in the files generated from version. 13 are 0.13 to 0.14.

B

So if there's just a new version, you can just click, commit build with no changes and we'll create a pull request, which has all the changes for the auto-generated file.

A

Awesome petra said this is awesome, I think so too. All right, um I will where we're getting to the end. This was really really insightful now for my little non-technical questions that I like to ask: what's your favorite food and what's your favorite beyonce song, if you don't listen to beyonce, what's your favorite song in general, no.

B

This is good so for favorite food, um it's a little difficult. My favorite food used to be sushi. I have become a vegetarian over the past two years, so it's like really difficult to find vegetarian sushi, um I mean yes, you can get an avocado roll, but that's that's not exciting. That's not what you go to get sushi for um so like now, I'm kind of leaning more towards like a vegetarian ramen. That's usually.

A

Easier to find.

B

As far as my favorite beyonce song, I am not a beyonce fan, that's not saying that I don't think she's talented. She definitely definitely is incredibly talented. It's just generally, not my style music. I actually wrote this down because I have this minor rant to get into. However, however, when it comes to like her songs, definitely my favorite song of hers, and probably in like my top 100 songs of all time, is uh hold up.

A

Oh yeah, that sounds good hold up, they don't let me let I get you and I'm vegetarian too. I've been vegetarian for all of my life, so I understand the struggle because back in the day they did not have like all these like burger. King did not have a impossible burger. So essentially I was just getting a happy meal at mcdonald's or whatever taking the meat out and just taking the like little toy, because I.

B

A

To be like my friends, I.

B

Get it it's cyber again, it's it's difficult being a vegetarian at times yeah, especially when your family isn't a vegetarian family. um I was a vegetarian once when I was in like my early 20s. I did it for a year and a half um come thanksgiving.

B

I buy sliced tofurkey because I'm like mom, can you just heat this up and I'll eat the tofurkey? That's fine I'll live with this, and I'm like okay, this tofurky turned out really good. I'm really surprised because this is like the deli slice of meat turns out. I didn't know this. Until years later, no my grandma was just taking the turkey broth and pouring it onto the tofurkey.

B

Oh no, no one decided to tell me this, like it's hard when your family is sabotaging you and there's nothing malicious in my grandma she's, like oh, the poor boy, he needs the turkey.

B

I love my grandma. I will always love my grandpa, I'm not even mad at her. It's.

A

Just hilarious yeah that is so funny.

B

Anyway, my my rant my rant about beyonce, okay, here's my issue: it's nothing wrong with her crime on the middle attack. Yes, okay, um issue with beyonce, so in 2008 she releases a song called telephone, great song, good song, whatever she does a remix with lady gaga, okay, 2008 beyonce, lady gaga, tel uh video phone, sorry, video phone.

A

I remember that video phone yep.

B

2009 lady gaga releases a single called telephone with beyonce, there's something weird about that. I I don't like how, within one year these two artists are getting together with a song. It's a video phone. Every phone is every telephone. Every telephone is a video phone. There's something up about that it. It doesn't sit well with me. It's such a stupid thing to complain about I get it, but like do they think we wouldn't notice and we didn't notice.

B

I didn't notice this until last night I was going through a dystopia because I couldn't remember the name hold up. I know the song like I'm singing to myself, but I could not put the name so like I'm going through. I see 2008 uh uh video. If I'm like. Oh I like that song, I saw lady gaga, I'm like oh yeah, that's the song. I really liked it because I used to like lady gaga. Then I saw a telephone like wait. Wait what.

A

You're, like what are you all trying to do here.

B

Not an important rant. I only realized that 13 years later, but I think there's something sketchy about that and I'm just I'm just putting that there for, uh for you all to enjoy.

A

I love that that was great. That was great. I think this is a perfect note to end on a little little rant about about um video phone and telephone bakari said this is hilarious, all right, y'all. Thank you so much for tuning in. I hope you learned a lot. I know I did, um and I think this was a pretty fun stream, um see you next friday. Thank.

B

You for having me.