Day One
Today we made our name tags to show people who we were, and if they didn't get to see that, then we played a fast name game to get to know each other better. Now, I know everyone, but not their names, but by the food they said they were. Haha. Then we played Jeopardy, sorry I have no idea how to spell that, and it was very fun. My team had the least points, but it was very fun still. I would scream carrots. Yep. SO that was day one.
Day Two
Today we had a woman come in and introduce us to a new coding language. At the moment I have forgotten it but I will get it again at some point. We learned how to operate and control the program and it was very hard for me. When we code, I am not very good at knowing what the next steps on my own would be, so I go along with everyone else, but when she said to do our own names, that's when I started to freak out. I don't know how to make a little turtle spell Izzy! Sorry but that's just me. My friend Taylor was super good at it but it just didn't click with me. So when they announced we would be doing robots the rest of the day that's when I knew we were all good. I like and feel I am the best at those out of all the things we learn here, so I was super excited because I thought it was LEGOS. But when I found out it was not, I was slightly disappointed to not have LEGO'S, but it was fine, I mean it was very fun to screw in the screws, that was my job, but sometimes it got too hard and we had to ask (many times) for some help. I really hope that wasn't annoying! So yes, that was day two.
Day Three
Today we continued the projects we began yesterday. We worked on a new project on the coding program (still forgot the name) and we are doing one based on some scientific data. It's on like pesticides leaking in the ground or something like that. I don't really know, because she did not explain it. So once we did some coding (and we did a lot compared to yesterday) and that was somewhat fun. I don't really like this data project much. So then we switched back to the robots and we did so,e finishing touches and then we began to hook up the Adrino board. Did I spell that right? Let's hope so. The coding is familiar to me because I have used this program before, but I needed a nice trip to memory lane that I was not given. So we had to wing it, but it came out fine and now we have a pretty funny program. I love working and building the robots. And, today is Movie day, so I am super excited for that. Me, Taylor, and my little sister Kat are going to all come and watch. I really hope it's fun!
Day Four
Today we finished our NetLogo projects. And I finally remembered what the name was today. But we did. I had a super fast whatever like data, I was on the pesticide team and mine sunk through the diagram really fast and I was done a lot earlier then Taylor. The funny joke we had the whole time was how long hers was taking versus how long mine was, and it was very funny. I finished early and I got a lot of candy in the process. Then we moved back to Boebots. We added some stuff (wires and such) to our robot. Taylor was too scared to do it because she thought it was going to shock her, so that also was very funny. I have worked with these wires before, so I wasn't as worried. We are learning how to make sounds on our BoeBot who we named Bo by the way, and it was very annoying with a simple tune and it took us awhile but we got a small tune. When the whole board fell off, we ad to fix it and work some more, but then we were fine. Then we needed to add some whiskers. These were a huge problem. Every single camp leader (especially Belle thanks man) and we were trying to work all these out. We did some coding as a class and called it a day. After some very confusing coding, which was longer then I thought it was going to be, we cleaned up and got ready to go. And here I am! Also, today was very fun for Disney Day, I wore my ears and brought a stuffed animal dressed as Tigger. Oh, and the movie night was very fun by the way. Thanks!
Day Five
Today was a more relax and have free time day. It wasn't "free time", but it was pretty close. I finished up some graphing from our NetLogo project on my foldable and then me and Taylor decked out our Boe-Bot. I am a little sad to see it go because we even named her. Bo, with a personalized cut out sparkly bow. We got to decorate them, so she's all glitter from her wheels to the top of her crown. Today we haven't done much, and it's more of a finishing up day, so no one is doing anything in particular. Which makes me sad because normally these are super long for me, but I guess today wasn't super long either. I'm writing this in the middle of the day, so maybe there is more later.We shall see. A few hours later, they set up a maze we had to have our bot go in and not kill itself in the process. Our robot's whiskers are messed up. When we adjust the whiskers, they mess themselves up and make our robot spin in a never ending circle. and it's very annoying. At the moment we are still fixing it so it won't do this anymore, but it's still being worked on to the point I have a feeling we will leave our bot not working, which is very sad. But still, today was very fun and I had lots of fun. I really hope next week is just as good as this one!
Week Two, Day One
Today we began our unit in Cyber Security. Sasha was going over the basics of hackers and how easy it is for someone to hack you. we learned how to detect fake emails and saw a few videos on how easy it is for people to hack you. Then we moved on to the Adruno Uno unit which was fun for me. I have used them before, so this was a nice review, but I still had a lot of fun, because I don't want to sound cocky saying that was review huhuhuhuh but it's just like a nice reminder because I forgot. We are running out of time and I really need to do my survey. Normally my blogs are a lot longer, but I have like no time today. It was very fun!
Week Two, day Two
I am super sad because I already wrote today's but it deleted it and now I am super sad but I can recap maybe as fast. I like my blogs to be long but I can't if I don't have any time :(. Anyways, today we learned the Ceaser thing with Sasha. I have already learned this, but I always am confused with it so I was paying attention to the lesson. I hate it. It's super hard and not very easy. Instead of having to write the alphabet a lot and try and guess the number of times over and be wrong and have to write it again, I instead just figured out one number and then I used context clues and figured it out. This took the majority of the day and then we had an hour to work on our UNO boards. Because of the lack of time, we did just a free coding time and I was working on the super awesome and detailed blog, but I pressed something and it was gone. SO here is it's sloppy seconds. Today was very fun thought. Thank you!
Week Two, Day Three
Today we made our own encryption codes. It was very fun for me because I think mine will be hard to solve. Before when I did this with Nicole I made the Ceaser thing shift, then i jumbled up the letters of the answer thinking that would be really hard. Spoiler. It wasn't. So this time I was determined to do something better. I wanted to do something like it but I wanted to make it harder. I really hope I can explain it well enough here, so here we go. I shifted our alphabet over seven times or something random like that, then the code was jumbled (duh..) then the code was a bunch of numbers. This might trick people because they don't know what they mean, but if they do it right they should add them all and get twelve. Once they do, you should figure out to shift the alphabet twelve times for the last code for them to crack, which is a lot of number again, but it says "times" so they know to multiply, but in the end (and it's not too many numbers) I put "times zero" so they did all the work for nothing :). Then we worked on our UNO and we did morse code today. I would say the hardest thing was having to writing all the letters and not make mistakes because I did a lot and it was long and I had to pee so yeah. Then Analyssa told us she was going to have us take it apart and we were all super mad so she gave us another day. So that was today. I might come to the Minute to Win it tonight!
Week Two, Day Four
Yesterday we worked on our Audrino Jars a lot. I painted mine, and ask Belle it was an absolute MESS. I grabbed some clear-ish based purple sparkle paint that I coated my jar in it and then from there I tried to paint a moon but after some coloring problems, I had to re-paint the moon and it looks funny but the overall color is very pretty, but the moon looks eh. To make it not so plain, I painted YWIC on it and it isn't too bad. What happened was I outlined the moon, all was well, it was normal yellow, and it was fine, but then after painting the whole thing purple, I tried to outline the moon with some black so it would work better, but that did nothing but mess it up. Once I outline it incorrectly, I thought it was a good idea to blend the messed up black and the very bright yellow. A greenish color was the result of that. After about half an hour of absolute badness, it was ok looking after wiping it all off. So that was yesterday.
2. What were the important learning targets of this project/artifact? (What were the requirements for the project?)
3. What were the computer science concepts used for this project/artifact? (Variables, loops, conditional statements, functions, lists/arrays, methods, etc.)
4. What were the computational thinking principles used for this project/artifact? (Abstraction, algorithms, correctness, efficiency, iteration or loop statements, variables, etc.)
5. How does this project/artifact relate to the “real” world? What did you learn or use that will help you outside the classroom?
6. In this project/artifact, what did you particularly want others to notice?
7. What would you improve if you could do this over again?
Today we made our name tags to show people who we were, and if they didn't get to see that, then we played a fast name game to get to know each other better. Now, I know everyone, but not their names, but by the food they said they were. Haha. Then we played Jeopardy, sorry I have no idea how to spell that, and it was very fun. My team had the least points, but it was very fun still. I would scream carrots. Yep. SO that was day one.
Day Two
Today we had a woman come in and introduce us to a new coding language. At the moment I have forgotten it but I will get it again at some point. We learned how to operate and control the program and it was very hard for me. When we code, I am not very good at knowing what the next steps on my own would be, so I go along with everyone else, but when she said to do our own names, that's when I started to freak out. I don't know how to make a little turtle spell Izzy! Sorry but that's just me. My friend Taylor was super good at it but it just didn't click with me. So when they announced we would be doing robots the rest of the day that's when I knew we were all good. I like and feel I am the best at those out of all the things we learn here, so I was super excited because I thought it was LEGOS. But when I found out it was not, I was slightly disappointed to not have LEGO'S, but it was fine, I mean it was very fun to screw in the screws, that was my job, but sometimes it got too hard and we had to ask (many times) for some help. I really hope that wasn't annoying! So yes, that was day two.
Day Three
Today we continued the projects we began yesterday. We worked on a new project on the coding program (still forgot the name) and we are doing one based on some scientific data. It's on like pesticides leaking in the ground or something like that. I don't really know, because she did not explain it. So once we did some coding (and we did a lot compared to yesterday) and that was somewhat fun. I don't really like this data project much. So then we switched back to the robots and we did so,e finishing touches and then we began to hook up the Adrino board. Did I spell that right? Let's hope so. The coding is familiar to me because I have used this program before, but I needed a nice trip to memory lane that I was not given. So we had to wing it, but it came out fine and now we have a pretty funny program. I love working and building the robots. And, today is Movie day, so I am super excited for that. Me, Taylor, and my little sister Kat are going to all come and watch. I really hope it's fun!
Day Four
Today we finished our NetLogo projects. And I finally remembered what the name was today. But we did. I had a super fast whatever like data, I was on the pesticide team and mine sunk through the diagram really fast and I was done a lot earlier then Taylor. The funny joke we had the whole time was how long hers was taking versus how long mine was, and it was very funny. I finished early and I got a lot of candy in the process. Then we moved back to Boebots. We added some stuff (wires and such) to our robot. Taylor was too scared to do it because she thought it was going to shock her, so that also was very funny. I have worked with these wires before, so I wasn't as worried. We are learning how to make sounds on our BoeBot who we named Bo by the way, and it was very annoying with a simple tune and it took us awhile but we got a small tune. When the whole board fell off, we ad to fix it and work some more, but then we were fine. Then we needed to add some whiskers. These were a huge problem. Every single camp leader (especially Belle thanks man) and we were trying to work all these out. We did some coding as a class and called it a day. After some very confusing coding, which was longer then I thought it was going to be, we cleaned up and got ready to go. And here I am! Also, today was very fun for Disney Day, I wore my ears and brought a stuffed animal dressed as Tigger. Oh, and the movie night was very fun by the way. Thanks!
Day Five
Today was a more relax and have free time day. It wasn't "free time", but it was pretty close. I finished up some graphing from our NetLogo project on my foldable and then me and Taylor decked out our Boe-Bot. I am a little sad to see it go because we even named her. Bo, with a personalized cut out sparkly bow. We got to decorate them, so she's all glitter from her wheels to the top of her crown. Today we haven't done much, and it's more of a finishing up day, so no one is doing anything in particular. Which makes me sad because normally these are super long for me, but I guess today wasn't super long either. I'm writing this in the middle of the day, so maybe there is more later.We shall see. A few hours later, they set up a maze we had to have our bot go in and not kill itself in the process. Our robot's whiskers are messed up. When we adjust the whiskers, they mess themselves up and make our robot spin in a never ending circle. and it's very annoying. At the moment we are still fixing it so it won't do this anymore, but it's still being worked on to the point I have a feeling we will leave our bot not working, which is very sad. But still, today was very fun and I had lots of fun. I really hope next week is just as good as this one!
Week Two, Day One
Today we began our unit in Cyber Security. Sasha was going over the basics of hackers and how easy it is for someone to hack you. we learned how to detect fake emails and saw a few videos on how easy it is for people to hack you. Then we moved on to the Adruno Uno unit which was fun for me. I have used them before, so this was a nice review, but I still had a lot of fun, because I don't want to sound cocky saying that was review huhuhuhuh but it's just like a nice reminder because I forgot. We are running out of time and I really need to do my survey. Normally my blogs are a lot longer, but I have like no time today. It was very fun!
Week Two, day Two
I am super sad because I already wrote today's but it deleted it and now I am super sad but I can recap maybe as fast. I like my blogs to be long but I can't if I don't have any time :(. Anyways, today we learned the Ceaser thing with Sasha. I have already learned this, but I always am confused with it so I was paying attention to the lesson. I hate it. It's super hard and not very easy. Instead of having to write the alphabet a lot and try and guess the number of times over and be wrong and have to write it again, I instead just figured out one number and then I used context clues and figured it out. This took the majority of the day and then we had an hour to work on our UNO boards. Because of the lack of time, we did just a free coding time and I was working on the super awesome and detailed blog, but I pressed something and it was gone. SO here is it's sloppy seconds. Today was very fun thought. Thank you!
Week Two, Day Three
Today we made our own encryption codes. It was very fun for me because I think mine will be hard to solve. Before when I did this with Nicole I made the Ceaser thing shift, then i jumbled up the letters of the answer thinking that would be really hard. Spoiler. It wasn't. So this time I was determined to do something better. I wanted to do something like it but I wanted to make it harder. I really hope I can explain it well enough here, so here we go. I shifted our alphabet over seven times or something random like that, then the code was jumbled (duh..) then the code was a bunch of numbers. This might trick people because they don't know what they mean, but if they do it right they should add them all and get twelve. Once they do, you should figure out to shift the alphabet twelve times for the last code for them to crack, which is a lot of number again, but it says "times" so they know to multiply, but in the end (and it's not too many numbers) I put "times zero" so they did all the work for nothing :). Then we worked on our UNO and we did morse code today. I would say the hardest thing was having to writing all the letters and not make mistakes because I did a lot and it was long and I had to pee so yeah. Then Analyssa told us she was going to have us take it apart and we were all super mad so she gave us another day. So that was today. I might come to the Minute to Win it tonight!
Week Two, Day Four
Yesterday we worked on our Audrino Jars a lot. I painted mine, and ask Belle it was an absolute MESS. I grabbed some clear-ish based purple sparkle paint that I coated my jar in it and then from there I tried to paint a moon but after some coloring problems, I had to re-paint the moon and it looks funny but the overall color is very pretty, but the moon looks eh. To make it not so plain, I painted YWIC on it and it isn't too bad. What happened was I outlined the moon, all was well, it was normal yellow, and it was fine, but then after painting the whole thing purple, I tried to outline the moon with some black so it would work better, but that did nothing but mess it up. Once I outline it incorrectly, I thought it was a good idea to blend the messed up black and the very bright yellow. A greenish color was the result of that. After about half an hour of absolute badness, it was ok looking after wiping it all off. So that was yesterday.
1. Provide an overview of your project/artifact. (For example: I designed a video game using Scratch programming where the player, or snowman, has to catch 5 snowflakes and avoid the flying flames.)
2. What were the important learning targets of this project/artifact? (What were the requirements for the project?)
3. What were the computer science concepts used for this project/artifact? (Variables, loops, conditional statements, functions, lists/arrays, methods, etc.)
4. What were the computational thinking principles used for this project/artifact? (Abstraction, algorithms, correctness, efficiency, iteration or loop statements, variables, etc.)
5. How does this project/artifact relate to the “real” world? What did you learn or use that will help you outside the classroom?
6. In this project/artifact, what did you particularly want others to notice?
7. What would you improve if you could do this over again?
8. Does this project/artifact reflect the effort you put into it? Why or why not?
1. We did three projects. One was our NetLogo, which wasn't my best because I gave up after we moved on. It spelt an I. Do you know how hard it is to make it spell TWO Z's??? AND A Y???? Then we made our BoeBot, which we build (and because it was not a LEGO build it was hard but very fun) and we named ours Bo(with a small bow on the O so you could tell it was a she). One of her whiskers was a brat but after Zack came over he fixed it and we were all good on that. Then we did our Jars with the lights which was very fun. Analyssia gave me a huge light instead of the smaller ones and I love it!
2. For NetLogo we needed to use a lot of components to have it work correctly (making the pen thing spell our names ) and that needed so much I can't remember them all. The BoeBot was easier coding wise because all we needed to do was code the whiskers to turn around when they sense something and have it on a loop. For our Lightup Lamps we needed loops and variables and all that.
3. I used loops, augorithums, computational thinking, I used it all!
4. I used the same things, i don't understand what is different about these questions...
5. For NetLogo we did a project on the pollution sinking into the ground and our BoeBots can be used for anything that needs robots and I don't really know how lights and beeps on a bread board can help... but yeah.
6. For my BoeBot we decorated it and gave it this awesome nametag that said "Bo" but we had a sparkly bow on top of the O so you could tell it's a girl. Then for my lamp I made it very pretty.
7. I would make my NetLogo finished, then I would give my BoeBot some beeps, then I would erase the moon I messed up on my lamp.
8. I think I worked hard building our robot and on our laturn. Yay.
Comments
Post a Comment