⚙️ General Mayhem reporting from the archives!
Team Trial & Error Robotics traveled to Oxford for the Mississippi FIRST Tech Challenge State Championship, where our trusty robot Cuttlefish battled through intense matches, historic high scores, and fierce competition.
Did we survive the mayhem?
You’ll have to read the adventure to find out!
Trial and Error Robotics is a nonprofit community-based FIRST Tech Challenge team. FIRST Tech Challenge, or FTC, is an organization that aims to inspire future leaders in STEAM. Every year, FTC teams are given a new and exciting challenge to solve. Our team aims to complete this challenge by designing and building a new robot…
Hello everyone! It’s your favorite chaotic engineer, General Mayhem, here once again to report on the latest adventures of Trial & Error Robotics. You may be asking yourself, “What sort of STEM-fueled mayhem has the team gotten into now?” Well, prepare yourselves, because this time our mission took us to Science Unleashed at the Engineer…
Hello everyone! It is your favorite General here with another exciting report on the adventures of Trial & Error Robotics. Today, we’re talking about one of our latest missions into the community to help our fellow neighbors—so let’s get to it! Our intrepid robotics team recently assisted with Murals in Action, a living history project…
General Mayhem reporting for duty! Over the past few weeks, Trial and Error Robotics has been out bringing STEM to Vicksburg! From Elevate’s Family Day to the Spring Flea Market at
the Old Courthouse Museum, our team had an
incredible time meeting families, showing off
technology, and raising support for the future of
robotics in our community. Read more about it in our latest article.
Hello everyone! It is I, General Mayhem, and I am here to tell you about what happened on March 28. Our team was tasked with assisting Forestry Products with their Easter Family Day event. There were games, food, and even one noble team member was brave enough to don some rabbit ears and help bring…
Trial and Error 10191 