Coding and Robotics Student Leadership Body
At the start of the 2022 school year I applied for and was appointed as the secretary of the Coding & Robotics Pathway at COHS. My job as a secretary is to make sure member hours are logged in, and assist in the development of events that we wish to host.
Clubs
Computer Science Honor Society (CSHS)
Near the end of the 2021-2022 school year I was elected as CSHS secretary. As Secretary, I have configured a system to help log in meeting and volunteer hours of the club’s members, as well as having active involvement in lesson instruction.
Elk Grove Computer Science League (EG CS League)
I have been a member of the EG CS League since the year it was formed (2021). I have attended many of the EG CS League's workshops to expand upon my knowledge of computer science, learning topics such as AWS, interface design, and more. Over the 2022 summer, I attended an EG CS League AWS community service workshop, which conceptualized on the fundamentals of AWS and used them to create meaningful community service apps. I have also worked with EG CS League in the development of a Spring hackathon, representing the Coding and Robotics Pathway Student Leadership Body.
Volunteering
I have volunteered in multiple computer science events as well. As I mentioned earlier, I participated in the EG CS League AWS community service workshop. Alongside this, I have also volunteered at a few VEX Robotics tournaments. The volunteering tasks we did include testing the robots for qualification, resetting the fields, and finishing disassembling the tournament setup.
Battle Bots
In February 2022, my friends and I took part in a Battle Bots tournament called "Sacramento Bot Battles." We had only two months to test and build a respectable bot, a considerably short amount of time. Everyone in our team was inexperienced and adding to the factor that we were short on time, we had to cram in a lot of work. We first began by formatting the design we wanted to achieve and split our roles in the team. We did a lot of research and looked up a lot of tutorials to understand the functionality of the bot to meet the rules of the competition. However, even with many afterschool hours put in we were not able to have a metal chassis for the bot due to time constraints. Our final design was a 3D printed chassis, with additional metal bits and a metal wedge, and the bot was named "HaleStorm," after our beloved coding and robotics teacher. We went with what we had, hoping that we could at least gain a learning experience. Unfortunately, our first round didn't go as well as we had hoped. We lost, and the edges of our bot's chassis became loose, which resulted in the inside parts of our bot being thrown out. Our bot was demolished, however, we voted that we should try to assemble what we could to compete in the next round. As a team, we worked quickly to reassemble the bot, and I feel that this was the most valuable part of our trip, as we gained experience on how to deal with and recover from a losing situation. Our result was "HaleStorm 2.0." Even though we lost again, our bot did much better in the second round than it did in the first, therefore I was happy with our overall experience at the tournament. We look forward to the next Battle Bots competition, with a better overall Battle Bot, and recruitment of more members.