Skip to main content

a necessary reflection: scioly @ Upenn

 




      I had a fun time going to Philly (again!) to participate in Materials science and Codebusters events of scioly. Though I learned a lot while briefly prepping for these events, our results were disappointing (54/65 place overall and the highest score was Matsci with 33/65).


 Instead of taking this failure to heart however, I thought over it and decided to split this point into IMPROVEMENTS and THINGS I LIKED ANYWAY. 

IMPROVEMENTS:

                                                             

"Nothing in this world can take the place of persistence..." -Nikola Tesla 

As a sophomore / new to this team, it seems like my responsibility to help run the team next year. I'm clear that the fault is not with our potential but rather with our organization and lack of practice-- the club is not hyped up enough, and once again we were given assignments last minute unlike every other school. Instead I propose:
- Earlier tryouts 
-Even split of grades in the team (not too many seniors as they are either overloaded/have senioritis at this time) 
-Regular meetings where we give mock tests
-Taking build events more seriously! (these are supposed to be the easiest but due to a lack of prep, these were the ones that went the worst) 
-hyping the club up to the freshies! (including them and encouraging them next year!) 

I took it upon myself to stalk our school scioly record for the past few years, did a clear analysis-- and I think these measures can lead us to victory next year.  I also talked it up with the two other sophomores on our team and we are so ready to help our school do much better next year! 

failure? nahh...everything is a learning experience :) 


                                                            
*Proud of myself for solving aristocrats: I got time bonus for our timed question on Codebusters!! (I need to practice more for this event, but I had a fun introduction to it this year-- apparently our school has never gotten a timed question before, and I'm having fun deciphering things...very relaxing) 
*I learned about Matsci and now I can apply this to my autoshop club! (I understand injection molding) 
*I learned how to make...cement!!! Did you know that cement dust particles can cause health problems due to acting almost like glue in your throat after you breathe them? Our cement worked very well! 
*Got Starbucks with friends : )  and learned that UPenn is BEAUTIFUL 
*Also learned that schools that are good treat scioly like mun...have a better perspective for the club in general now and how to improve myself and the club! 
*Found out PUZZLE BARRONS from a fellow codebuster and plan to practice everyday since I exhausted the scioly website for codebusters in the few days I got to prepare. 

Grateful for this amazing experience and plan to move better ONWARDS! 




Labels:

Comments

Post a Comment

Popular posts from this blog

Undershirt to mitigate + monitor late effects of breast cancer [Seamless]

This was my final project at BWSI, and part of the reason I received the Dr. Bob Berman Disruptive Tech Award for e-textiles this year for BWSI. I'm so excited about it and plan to continue it in the coming months.  I have so much to say in this post, but for now I'll just share screenshots of my portfolio document and go on and on about it when I'm not compromising on sleep lol: Up Next:  -Experimenting with more motors  -Inserting batteries  -Expanding health monitoring UI! 
Post a Comment
Read more

NOTHOLE

nothole in the making...still integrating the sensor and ESP here what is a...nothole? Nothole is a sensor system on a car that can sense potholes + their severity + their location, and send this back to a central server application that can consolidate this data for usage by government officials and construction workers to provide for more efficient repavement of roads. This project won my group 1st place in HackMIT Blueprint's beginner track!  we had two parts: sensor (ultrasonic sensor) + server system via ESP8266   So technically...pothole detection has been done before (there are whole articles on it). What HASN'T been done before is consolidating it on a server. Ideally, we wanted to make a Google Maps application (using the JS API) but couldn't since we ran out of time in the 7 hours we had to build this. My partners, Jasper and Alex, focused on making the ultrasonic sensors work without fault + setting up the demonstration. On the other hand, I spent my hours figu...
Post a Comment
Read more

Pennapps '25 + Sunscreen Reminder Shirt (Soliss)

^^meet wearable Soliss  So I spent most of last weekend on the floor of UPenn's Levine building (crazy deja vu I was literally right here for Upenn scioly in March). I slept 7 hours of the 36 hour hackathon and coded like mad for the rest of it (no seriously I fell asleep while CODING). I didn't win an award this time, but built a super cool FUNCTIONAL WEARABLE : D (I applied skills from BWSI!)  1) What is Soliss? Over my 36 h - 7h = 29h journey, I built Soliss with a team I found at the hackathon. This was a wearable that could track excess UV radiation hitting the skin and remind the wearer to reapply sunscreen. The wearable also connected to an app which allowed the user to track overall danger levels of UV radiation on their skin (calculated via a formal algorithm, and personalized to the user's demographic etc). Personally, I created the wearable part of the project (so all the hardware etc). In my 29 hours I prototyped/designed, breadboarded, coded, and the hardest pa...
Post a Comment
Read more