April 19

Post #1-Choosing my topic

Finding my topic was generally hard, mainly because I had so many ideas. Since I am so interested in Technology, I decided that my topic would revolve around Technology. I had 4 topics that I wanted to do. My first one that I wanted to do is generally how AI powered robotics improved humans, but that was very broad, and although Ms. Edwards said to start broad, it was way too broad. The topic was interesting though and came to my advantage because then I later realized how the idea was useful because I was generally motivated to learn, and that I had as topic that I was passionate about, so it would be easier to find a topic by using a factor of me being passionate about topics.

Later on, I brainstormed topics that were related to AI Robotics, and then I came across some more: Data and research gaining from AI based computers medically related topics, and also how AI chess computers are programmed, and also how they have affected humans play better chess, and generally gain more knowledge about the chess industry, including history. I thought these 2 newly developed topics were very interesting, and I wanted to more deeply research them. I then used the same method that I used before, determined to see what can even further motivate me, and generally what I would be the most passionate about in the long term. What I decided I would be the most passionate about in the long term is AI data gaining from computations medically related topics. This translates into AI based computers gaining knowledge from historical cell actions made by scientists, which really interests me because is it technology related, but also generally improves humans and is more efficient which I also deeply care about.

And then after that, I finally used all of the information from research and attempts in choosing my topic to bring the medical topic down a little bit. I then choose as my final topic which is about the robotics doing surgery for humans, and not the robotics that do the surgery are the main focus, Burt the main focus is then the robots that do the surgery physical of the surgery, then robots that do the surgery collect data from the surgery, computers analyze the information, and the humans then program the Robots to do better based on the data that the computers collect from the robots in the first place. I also was wondering how can we improve this formula of surgery, so this ended up to be my topic: the data that is collected from robotic surgery, and how the data provided by the robots that do surgery can be improved so that the robots can do better surgery.

Generally speaking, there were many complications revolving around my topic selection, but I used my failures to motivate me and to better pick a topic. It was stressful, but I have to stay optimistic if I am going to survive this long journey.

March 25

Post #3-Getting more advanced with Tynker

My third coding project was on Tynker, called the Platformer game. I decided to make it using the fundamentals of what Tynker provides, and then experiment and create further. Because of how Tynker conceptually layed out the project, I had an easy time interpreting which blocks to use, but also more importantly, not having to gave Tynker come down to its disadvantage by not having a couple of desired toggles for the user. What I mean by that is because earlier in my Tynker experience their were a couple of fundamental blocks that Tynker lacked that Scratch had, or didn’t lack. That generally in the coding language make it easier to access understanding of how to code. This made it easier for me to follow the guidelines without having to worry about a specific toggle not being their. It had some code in the start front he Tynker fundamental structures, but then I experimented and customized the game so that it would be more authentic, and interesting at the same time, which generally I think made the book interesting.
Anyways, generally using the same principles that Tynker provides and now that I am expanding my knowledge of the coding language has now enabled me to create more authentic and interesting games at the same time. This blog post was short, but I think that it will get the message pretty clearly to the reader. Here is the game:

 

March 25

Post #2-How my second project on Scratch further enabled me to express me creativity and innovation

The second project that I did, I did using Scratch. Scratch for me was really impressive by the means of how it enabled me to express creativity and iteration. Their were a couple of things that I did not like about Tynker, which include some of the toggles not being able to access on them user’s perspective. That included a few toggles that you bring into the coding sequence that is good to have in your toolbox to refer to, such as the voice responding system toggle that their is in Scratch. Scratch was very good because it enabled games like an automated system to talk to you. Anyways, I was more impressed with the performance of Scratch and that enabled me to make a better project in general. I made a Scratch game that was where you could move a character, and the character who is a cat can shoot a ball to intercept another ball consistently firing randomly with the goal of minimizing your hp (hit points) to zero. When your hp is at zero, you lose the game. The goal s to minimize the ball’s hp to zero, then you win. It is a fairly simple game that required some basic coding, but the conceptual standpoint of this specific game really helped me understand some of the more basic concepts of coding, which later on will definitely help me to know.

I think that I learned how to differentiate what is right and wrong by experimenting a basic concept, and that enabled me to be more accurate with troubleshooting and have a better understanding of the coding language in general. This gamed helped mefeel more confident in the coding language and how that is going to make me better at understanding general aspects in life, even outside of coding.

Here is the project:

 

March 25

post #1-how Tynker has helped me understand the basic conceptual standpoint of the coding language

Hello. My name is Aidan. My coding experience so far covering my two basic projects has been stressful, but at the same time enabled me to more deeply how really everything technology related operates, but obviously in a less sophisticated manner. My first project I did on Tynker, it was about when you touch an animal, it makes various songs. The instruction manual was very good by the means of how it really helped me with understanding the newly introduced coding language. It explained it in a very inspirational way, which encouraged me to continue to share my ideas by coding, and rally made me just feel good about coding. The stressful part was troubleshooting the problems that I encountered a lot of times. I became very addicted with making it so perfect that it was too time consuming, but the good thing is that I was very determined to complete my goal.

In general, my first project was really nice because the way I was introduced to the coding language, and the determination that evolved from Tynker to complete my goal. So far I am loving this coding experience with Tynker! this is my game that I made:

March 25

Blog Post #4-my last coding project and my general experience during the coding project

The last project for my coding project that I mad 4 is simply called the ping game. I chose this name because the objective is to using your mouse, to be able to use the green bar to control the ling pong ball, and not let the ping pong ball touch the ground. I called it the pong game because the general objective was related to the nae, “pong”. Anyways, there was a lto of elaboration in the form of coding implanted into this game. First, I used a asic Scratch guideline to help clearly direct the position that I desired to follow so tba i would have a clear objective on how I wanted to move forward with this game.

Then, I decided to put some other aspects in the game such as airplanes, and also have the bar that you use to keep the ball from hitting the lava so that you don’t die and then I made a health bar for the bar. The objective is that you have to avoid the enemies, and avoid the enemies 20 times, before you lose all of your health and you lose the entire game. There was some more advanced coding, but this blog post is more reflecting on how over the course of time, I was able to do more exciting and more sophisticated projects, because in general when I started this project I don’t know how to code.

I generally feel good because how I have progressed through a large and fancy timeline, which really helped me in general be a better coder, and how technology and Software engineering generally relates to our world and more explicitly and clearly in the future. In general this project was sometimes origin because of how time consuming it was, but in general all of the work paid off because it was another big aspect of the technological word, which generally speaking I love when it is related to Apple. I have had a great experience during this coding project. Here is the embedded game link:

March 15

Ignite presentation reflection

I think that my ignite presentation was very descriptive,and the presence of me was very good in terms of how I spoke. I was very nervous, but looking back I didn’t look nervous at all. I felt like I showed some natural presenting skills and the general style was very constant, and kept the viewers interested. I also think that the hard work paid off. I am used to presenting and speaking in front of a lot of other people, I was able to use that statistical standpoint to my advantage, especially because i just imagined that the audience was not their. In the Keynote presentation that  did to my family over Christmas break, I was presenting in front of more people than this cass, and I realized that it was the experience of learning for the audience, and their was really nothing to be worried about because the people that are watching are here to learn, and by presenting an interesting topic, they will enjoy it. It doesn’t matter if you mess up a little bit, because the audience has no idea on hat commentign looks like. Anyways, I have had a t of experience presenting in front of large audiences, (even in piano recitals!) and that has made me less nervous, and especially because realizing that the audience is on your side. Despite all that I think that I did well, their were a few aspects that I could improve on for the future, such as:

  • Incorporating the audience in the presentations to make it more interesting
  • Smoother transitions (just timewise, because I kept talking when I planned to say the content on the next slide)

Generally speaking, I think that I did a good job because I sowed some natural presenting skills,a and I also really worked hard, which payed off well. Here is my video, and the comments for my Ignite presentation, and also the feedback that I got from my classmates. Check it out:

 

This is the feedback that Ignite for my Ignite Presentation;

March 4

My first coding experience using Tynker (Post #1)

Hello. My name is Aidan. My coding experience so far covering my two basic projects has been stressful, but at the same time enabled me to more deeply how really everything technology related operates, but obviously in a less sophisticated manner. My first project I did on Tynker, it was about when you touch an animal, it makes various songs. The instruction manual was very good by the means of how it really helped me with understanding the newly introduced coding language. It explained it in a very inspirational way, which encouraged me to continue to share my ideas by coding, and rally made me just feel good about coding. The stressful part was troubleshooting the problems that I encountered a lot of times. I became very addicted with making it so perfect that it was too time consuming, but the good thing is that I was very determined to complete my goal.
In general, my first project was really nice because the way I was introduced to the coding language, and the determination that evolved from Tynker to complete my goal. So far I am loving this coding experience with Tynker!

February 14

Reflection on Debate unit Plastic Bags

In the video that was recorded of our groups final debate on Plastic Bags, whether we should or shouldn’t ban them, I think that in general we were all really well prepared, but I think the executing aspect of the debate (when I refer to debate I mean the final one in the video) wasn’t very good. Here are my reasons why:
Our debates didn’t show much energy:
I think that the debate didn’t show much energy because mostly we all were very nervous, I mean I know I was nervous, but I anticipated that the other group members (Ben, Emma, and Ayyan) were nervous too because it was an appearance. On camera, which initially does put a lot of stress on the reader, because it brings the mindset of them needing to be perfect, and not mess up on absolutely anything. Their were things that I noticed from all of our group members. I don’t want to give the input that I am criticizing anyone, I just wanted to remark different things that I noticed, to hopefully help those people, and me improve. I was personally “stealing the show”, because I barely let Ayyan speak because I had so much to say, and more things that I wanted it say. I felt bad for him after the debate because I feel like I stole a lot of the things that he initially was supposed to say. I also want to give a lot of credit to Ayyan because he decided to speak up a lot more than he usually does, although it wasn’t as loud as I hoped for, but it was a massive improvement, and I also understand that there was a lot of pressure because this debate was being recorded. Their were a couple of times that I noticed myself hesitating and not knowing what to say, especially when Ben brought up the point that people were losing their jobs because of the banning of plastic bans in some countries. I actually knew what to say in reality from some general knowledge and creativity, and a little bit of thinking on my feet, but when I paused for a couple of seconds I got terrified because of the camera, and was stalling by saying, “You mean the people that are losing their jobs are lowing their jobs because of the banning of plastic bags in certain countries?” (Which is exactly what he said and I already knew that) I also was thinking about saying, “Well then they can go get a new job like flipping burgers or something, but that would have been off topic. Another thong that I noticed is that Emma was extremely quiet, which was very unusual, but I think again that it was the pressure of the camera. Ok, so in general our debate didn’t show as much energy as I initially hoped for, but it got pretty elaborate at some points and I had a lot of fun. That’s what counts!
This debate unit was really fun and required some deep concentration and thinking in order to get the job done, and I also generally like debating because I have an opportunity to win with words, which I have discovered I have a big toolbox to refer from. Anyways, this unit was really fun and I wish we could do more of these related things. I loved this unit!

Here is the video of our debate:

February 1

Reflections and feelings on the Project (Building ans mental aspects) (Blog Post #6

I have been really deeply working on my Rube Goldberg project, and I over a long course of time have finally succeeded. This blog post that I am writing is trying to push some of the aspects, or lessons that I have learned over the course of this projects duration. This project has taught me many different life lessons that I am very glad did. This blog post also covers my experience and thoughts after the project.
This project has taught me many different things. First, is has taught me to be patient, and to observe and to not over exaggerate from a problem, especially the mental ones, because his project initially made me very stressed. This project has taught me to be patient because of how stressful the project was. The reason why it made me so stressed is because of how a large portion of my plans didn’t even come close to turn out as I think they would. As I stated in the earlier blog posts, I think that one of the downsides of this project, specifically the way our teacher, Mrs. Edwards assigned it, is for our sketch to have a due date that is before the original project’s due date, in this case the movie reporting the project, and about your project itself. It is very reasonable to have the sketch due date assigned before the movie reporting the project, but I think that since I made countless changes compared to how my sketch stated the steps would be, it was very hard for me to “have the cement harden inside the ground structure of the building.” In other words, to have a layout before randomly trying to execute the project. I don’t want to make it seem like I am criticizing anyone, I just have a strong suggestion that I actually think is good for Mrs. Edwards to consider when she hands this project out to her next year of yet to come students. Anyways, the project has taught me persistence because of all of the stress in the project that I encountered. The persistence aspect of the project that has taught me really helped me improve my thoughts and actions in general because it taught me to not overreact to something that is stressful, or that gets in your way. It is like a physical obstacle, but not one that is meant to be avoided, rather one that is meant to be matched with the will of the mind.
This project has also taught me to handle/coupe all of my negative thoughts. It has helped me coupe them by simply testing my mental approach/strength with its intentions to annoy me. And believe me, this project did really annoy me. I really had to stay extremely positive and have a lot of motivation, or something that keeps me fueled that makes me feel like I have purpose, meaning a real reason to do what I am physically and mentally doing in the moment, not meaning because this project is an assignment, more of something that makes me feel like I am doing the project for a good reason, not because it is fun. Actually, I know this statement is really weird, but the motivation that I had mainly was from music. I would put my Beats on and start listening when I am doing the project. Surprisingly this didn’t minimize my concentration, it just made me have more energy and have a more positive approach in terms of my mental approach, which in general really helped me coupe the negative thoughts in this project.
Overall, this project has taught me a lot of things, but I only wanted to point out a couple of them, because then you would be reading 100 pages. I thought that these 2 aspects were the most important aspects/emotions that I encountered during this project. The reason that I love this a project is because it is fun, it inspires creativity, and really builds character and tests you in many ways. This project is one of the best and worst projects of all time! (It is bad because of all of the time it takes to complete, and how stressful it is)

February 1

Blog Post #4

I haven’t been writing a lot of blog posts in a while because I have really been spending a lot of time thinking about my potential machine and how to compensate my bad Sketch in the first place with a better and more clear vision on how my project will commence in the proper way. I have been thinking about ways to do this and I decided to use the same method to make a new sketch for my planned contraption. Right now the sketch is in the past, because it was already due last Wednesday, so the reason why I am talking about this is because I wanted to cover the information that I have not told because of this delayed Blog post.
First I want to talk about my sketch and how I managed to compensate for all of that time that I consumed on a unsuccessful sketch. The sketch was really hard, because in my opinion if you wanted to have a successful sketch, you had to experiment all of the aspects on which you plan to use for your contraption. Another way to think about it is the tools that you have on your toolkit, but in order to use them the best possible way, it is best to experiment and test before randomly using your tools without a clear purpose on the way you want to use the tools. And without really changing a majority of your Sketch because if failures in the testing, you pretty much have to start off with a new idea, or pitch in the holes in your Sketch that you are uncertain about. For me, it was very time consuming because I kept experimenting with no luck, trying to find a layout that actually works for my sketch. I don’t want to try to imply a negative feeling, but I wanted p endorses why it was hard at least for me to come up with a sketch, ad simultaneity do the other requirements, especially the blog posts. Ok. Enough of that. Let’s get into reality and what is happening right now.
Right now, which is after I handed in my Sketch, the rest of the project is coming really easily because when I had a successful and clear sketch, my layout for the rest of the building/executing part was very simple and straightforward. And especially since I have done a lot of experimenting for my sketch, I have some of the building part down already. What I am trying to say is that now I have a good sketch, the rest of my project is going to be so easy, and not as hectic. The sketch was really the hard part of this project, far more than the execution aspect of the project. Now, all is left in my way is the blog posts!