 Hello everyone! We are so excited that you are joining us today. We are live at CESA headquarters and we are here to talk about jobs in computer science. We're going to give you a peek inside a startup today. So thanks for joining us today. The first thing you should know is I'm Angela and I lead the community team here and that means that I get to work with teachers all over the world that use CESA and make sure that they have some ideas that they can share with other teachers and make connections and I might even work with your teacher or your teacher maybe has connected with teachers that I work with too. I was a kindergarten teacher for 15 years before I came to CESA and I actually live in Minnesota so I'm visiting CESA headquarters this week. Today we are going to meet some more people that work at CESA. We're going to peek at jobs that are here at a startup and we're going to explore some engineering vocabulary and answer your questions at the end. So keep thinking about what you might want to ask us but let's meet some CESA team members. So first! Hi everyone! My name is Maria Inez. I am a software engineer so that means that I write the code that makes the CESA app work and I work specifically on activities features so when your teacher assigns you an activity to do in the app that's all my team. Awesome! And I'm Chris. I'm also a software engineer also working on writing code but the code that I write is a little bit different. It works on keeping CESA fast and safe so that no one's able to get at your data who shouldn't be able to and so that you can keep using CESA without having to wait you know minutes and minutes and minutes for the page to reload. Awesome! Hey everyone! I'm Ashley. I work as a teacher success success specialist here at CESA. My job is that every day teachers all over the world send me emails with their questions about CESA and it's my job to read those emails and make sure that they get the help that they need so they can keep using CESA in your class. My team is also responsible for spotting problems that teachers may be having that may be someone like Chris or Maria Nez need to look at to fix. So CESA keeps running smoothly. I don't work in an office like a lot of other people. I work here at home. I live in the mountains outside of a teeny tiny coastal town in Maine so I get to spend all day with my dog and two cats. That sounds amazing! All right so we're going to peek inside CESA headquarters because who doesn't love to go backstage at places right? So first of all you should know that CESA headquarters is in San Francisco California. Like I said I work in Minnesota at my house and Ashley shared too that she's she's not in California either. So when you come to CESA headquarters this is what it looks like when you get off the elevator because we're on the seventh floor of a tall building and you'll notice it's kind of like a classroom. Lots of desks, tables. Nobody has their own office at CESA. It's kind of like one big open space. You'll notice we carry backpacks too so you might have backpacks that you're hauling your stuff to school with each and every day. So we do the same thing. We also have this area that's called the playground and this is really where we eat lunch. We have big meetings every Monday morning. We have a tea meeting. So everybody that works at CESA comes into this space. We also have these conference rooms. So these are the rooms that we're sitting in actually right now. So the one that we're sitting in is the one with the orange sign that you can see in this photo and I think it's called hopscotch and Ashley of course is working from her home. So she's using our webinar software to connect that way too which is pretty awesome. The other spot I want to show you is the kitchen. Kind of a snack area, right? We know that your brain needs to stay alert and focused when we're doing this work. Just probably like you at school have snacks. So we want to make sure everybody at CESA stays fueled and ready to kind of keep working and building. So let's talk about some of the jobs that happen or exist at a startup. So the first job, these are the co-founders. So this is Carl and Adrian and these two are the ones that thought of the idea of CESA. So they're kind of like the bosses but they really work with everybody each day. Then we have software engineers. What do software engineers do? So software engineers are the ones who talk to the computer in a language that the computer understands to get it to show you all the cool content that you're making on CESA. So everybody on the engineering team knows how to code like really well. Really well. All right and then we have the product team. Yeah. So the product team is our product is the CESA app. That's our product and so the product team is in charge of deciding well what does the CESA app do? How does it look? So they design the app and they work closely with engineers to tell us what to make the CESA app look like and do. Then we have the operations and teacher success team that Ashley is going to tell us about. All right. So operations is not like an operator, you know, like a like a surgeon. They're not operating on anything. These are the nuts and bolts of the actual company. So these are the ones who do all the paperwork and do all the filing and stuff like that. The teacher success team, like I said before, we handle questions from parents, teachers and sometimes even students. And then we have the partnerships team. So this team works with schools to make sure that they can get schools set up with CESA. So if your whole school uses CESA, they help those schools get set up or maybe your whole entire district uses CESA. So they would help with that too. Then we have the marketing team and I'm going to go to the next slide because it continues. We have the community marketing team and we're really responsible for making sure people know about CESA or that they could learn about CESA. So we work with teachers to make sure they have all the information that they need to keep going with CESA. And I think the thing to remember is collaboration is key. So even today at school, I'm sure you are going to have to work as a team. You're going to have to solve problems. You're going to have to figure things out and that's really getting you prepared for any job that you have in the future, but specifically working at a place like CESA. And we're going to show you some fancy words, some vocabulary that software engineers use each day. So let's get started. What's this first one? Do you want to talk about it? Okay, so code is the language that computers know how to read. So behind the scenes, the computer isn't talking to you in English most of the time. It's using ones and zeros and that gets turned into all these funny characters that you see on the screen right here. So yeah, code are the instructions that tell the computer what to do first, second, and what to show on the screen. It looks like a wow, a big jumble to me because I don't know how to do that. All right, what about this one? All right, so have you ever been using CESA and something doesn't work quite right or something gets messed up? When that happens, we call it a bug. And that means that there's some problem in the code that Chris just talked about that is not working correctly. So when we find bugs or you guys find bugs and you tell us about the bugs, us, the engineers have to go into the code and fix them so that things work well again. And sometimes you hopefully have not experienced this too much, but if an app gets a really big bug, it will crash and that means you kind of get kicked out of the app, you might lose your work. So that's really bad. We really hope that doesn't happen and we try hard to prevent that from happening. So another word that we use is pull request. So basically when we're coding up our work in order to prevent bugs and especially crashes, we review each other's work. So just like you might have your teacher check your work or maybe even have another student peer review your work, we do the same thing with the code that we write. Yeah, so I think another example is like I remember elementary school writing stories, like a first draft. And then you would write that first draft and maybe you would have a friend look at it and they'd say, oh, you should fix this. That's kind of what happens in a pull request. Yeah, that's exactly right. And then the back end, this is a part of the code that you hopefully will never see. This is when you try to load your image. This is all the servers that are talking to each other that are finding the correct image and sending it back to computer so that it can display. And then we have the front end, Ashley. What's this? Well, the opposite of the back end is the front end. So if you never see the back end, the front end is what you see all the time. So whenever you open the app, whenever you press a button, we call that the front end. Yeah, so the things that you get to use every single day in CSAS, the front end. So we're going to answer some of your questions and we're so excited to do this as our favorite part. Some people wrote in questions before, so we're going to spend just a minute answering this first question and we'll give you time to share some questions live that you want your teacher to type in. So Chris is going to answer this first question. So Ms. Smith's fifth grade class in Pennsylvania asked, how do you make coding secure? And how do you write a program that nobody can hack? Yeah, this is a great question. So we spend a lot of time trying to think about how someone who is trying to hurt CSAS or maybe trying to steal data, we try to think about what they might do to take that. And then we think about all the different ways that you can interact with CSAS, all the buttons you can press, all the things you can type into the keyboard. And we just write a lot of code on the back that checks to make sure that the only thing that gets saved are the things that you are trying to save, the content that you're actually trying to create, and nothing that someone is trying to sneak into the system. Yeah, that's a big job. So Ashley, I know you want to do a couple shout outs here for some classrooms that are live and we're going to go into some questions. So anyone you want to give a shout out to right now, Ashley? There are so many classes that are connected right now and they're asking a million questions a second and we love them all. I'm going to give a shout out to Ms. Clark's fifth grade class in Dublin, Ohio. We have Ms. Swallow's class. We have Ms. let's see, I'm not going to say this name right, Ms. Dominic, Ms. Dominic's class. We have Mr. McKinney's class. We have Ms. Kirk's class, Ms. Uttermark's class. We have Mrs. Schmidtman. We have Ms. Nappy's class in, let's see, oh, she's in Maine. Hi, neighbor. Yep, she'll give a few more shout outs in a little bit, but right now, here's what I want you to do. We're going to play a little bit of music here for maybe 30 seconds to give you time to talk to your teacher and share a question you want them to type in. That's also going to give us time to look through all the questions we have. Make sure your teacher types in your grade level and the location when they're typing in their questions. Let's take about 30 seconds to type those questions in. Here we go. Okay, we have so many questions coming in. We'll try to go quickly and see how many we can get through live here today. We're going to start with Ms. Brem's class, a seventh grade class in North Carolina. Hey, Ms. Brem's class. How long did it take to make the code when CISA started? I'm going to jump into this one. I didn't build the code when it started, but I was in webinar yesterday with the founders who started CISA. When they started, they took about three months to do the first beta version of CISA, meaning the testing version. Then I think they said about three more months, a total of about six months, to get to a point that they could have an app that other people could use. We're still building code for CISA all day long. Five years later. Yeah. There's a lot going on there that continues to happen. More questions coming in. Let's see. Boy, how often do bugs happen? This is Mr. Khan's class in Minnesota. Hello. How often do they happen? Well, we have little bugs that happen once a week or so, but the big bugs don't happen very often at all. Maybe once a month, something like that. We're very quick at trying to answer all the bugs that come in. Yeah. Sometimes there are itty-bitty things that are quick to fix, and other times it's a little bit more complicated. Sometimes we actually catch bugs before they go out. That's a big important part of the pull request process. When I get Chris to look at my code, sometimes he'll catch a bug and save us from actually releasing that into the wild. That's great. We'd like to do that. Ms. Clark's fifth grade class. Hello. You have so many questions that you've asked, which is awesome. The one we're going to answer is, did you have other jobs before you worked at CISA? Ashley, do you want to start? What other job did you have before you worked at CISA? Okay. Before I worked at CISA, I worked at every teacher's absolutely most favorite place on earth, Starbucks. I worked at Starbucks for 18 years. Pretty much my entire adult life, I was a Starbucks manager. I loved it. I said I was a teacher. That's what I did for 15 years before coming to CISA. What about you, Chris? I was also a software developer, but I worked in healthcare. I tried to help doctors take care of patients and keep track of all the data. Awesome. I was also a software engineer before coming to CISA. I worked at Google. You might have heard of it. A huge company that works on a ton of different things, but I worked on Android applications. If you or your parents have any Android devices, I was working on those. Awesome. Ashley, you want to give a few more shout-outs while there's so many questions. So many questions. Yes. All right. I shout out to Ms, is that Ms. Vinnie's class in California? We have, let's see, Ms. Morgan's class. We have Ms. Alfred's class. We have Ms. Berry and Ms. Irving's fifth grade class in Tallahassee, Florida. We have Ms. Marsh's class, her third grade class in California. We have, let's see, oh my gosh, there's so many, like the questions are moving and I'm trying to get the glasses. We have Ms. Glidoo's class. We have Ms. Brems class. Ms. Morgan's class looks like seventh grade. Welcome. Let's see, Mr. Lee's third grade class. We have, oh my gosh, you guys have so many questions that you've asked. It's amazing. Oh, great. I love it. I love it. We'll go back into questions because there's so many we still have to answer here. Yes, a lot. All right. Let's see. Okay. We are talking to Ms. Morgan is asking a question. I think this comes from Riley, who's in eighth grade. What kind of higher level education would you typically need to become a programmer? That's a great question. There are a couple ways to become a programmer, actually. One way is by going to school and studying computer science in university. That's what I did. But another way is sometimes people study something else in college but then decide they want to be a programmer and they do like what's called a coding boot camp, where they learn how to code in a shorter amount of time, like six months, and then they can be programmers also. Cool. And some people don't even go to school at all for it. There's a lot of free courses online, but going to school is a little bit easier because it'll be more directed and it'll that you'll like make connections that can help you find internships and jobs if you're at school. Awesome. All right. Shout out to Ms. Sandlin's class in California. They've been eagerly awaiting. We have so many more. Let's see. We got we got to give a shout out to Ms. Moitose's third grade class in Taunton, Massachusetts because she had so many exclamation points. All the exclamation points for her shout out. Oh my goodness. Let's see. Okay. So my goodness. So many questions. I love it. Ms. Chamber's class is here today, which is awesome. Ms. Hart's class is here. All right. Hi, Mr. Koski. Ms. Kool's class in Omaha, Nebraska. I don't know if I said your name right. I hope I did. What was your inspiration to make CESA? So I will speak for the founders that created it. Basically, they created CESA because Carl, one of the founders always asked his kids when they came home, what did you do at school today? And they were like, nothing. But they also worked with teachers in their first app called ShadowPuppet and realized that teachers were trying to find ways to make sure they could communicate with families and also let students share their learning. Even if they weren't using technology, maybe you're using materials in your classroom. How can all of that be captured and shared? So that's kind of how CESA came to be. So great question there. Thanks for asking that. Mr. Wells' class is a fifth grade class in Canada. They want to know what year was CESA published. So the very first time that CESA was released was in January of 2015. So we're coming up on about four years of CESA being in. So everybody can use it, which is awesome. What kind of education, Mr. Lee's third grade class in Canada wants to know, what kind of education do you need to be a computer programmer? We kind of talked a little bit about it, but what would you say quickly for that? Yeah. Well, the type of thing that you will learn if you're trying to become a programmer is things like how to write code and how to read code. So that again, that's the language that computers know how to speak. So you'll spend a lot of time understanding how a computer thinks in order to be able to tell a computer what to do. Awesome. Do you have any other tips? No, I think that sums it up. And I think the one thing I would say too, is if we think back to being in third through eighth grade, like I shared earlier, anytime you're trying to solve a problem or you're doing something that's really hard and you're like, I don't know what to do, you're preparing yourself for coding and problem solving and working collaboratively with a lot of people. So keep up the good work there. I think we just have, we're almost out of time, but I want to share one more thing, and Ashley maybe can prepare our final shout outs, but we want you to take advantage of this contest that we have. And I've seen a lot of great submissions already coming into CESA coders, some of you that are here today. But you can create the next CESA class icon. So our designers want some ideas from you. So this activity is inside CESA. So your teacher can find it today and share it with you if you have time. And you can design the next icon. We're actually going to choose three designs that our designer will actually use to inspire the next icons that go into CESA. So everybody in the world could see it, which is pretty awesome. So before we say goodbye, Ashley, are there a couple final shout outs to give? Because we're so excited that everybody can join us today. Yes, there are. We have Mrs. Wrapp's third grade class from Spring City, Pennsylvania. We have a hi to Mrs. Jacobs class in Newport Beach, California. Let's see, shout out to Ms. Ski's class. Hi, Ms. Ski. And then we have, let's see, Mrs. Dilly from Mentor, Ohio. And Ms. Uttermark's fifth grade class in Minnesota. All right. And then we have Ms., let's see if I can say it from Bend, Oregon. Ms. Sieberfeind's class is also here as well. We have so many shout outs. Ms. Ross's class. Oh my goodness. I wish we could just spend an hour just talking to everyone. Yeah. But I bet they have other things to do. Right? My goodness. Thanks so much for joining us today, everyone. And we can't wait to see what you think about the next class icon. We can't wait to see your design. So thanks, everyone. See you soon. Bye.