Interested in working together? Just fill out the form below. Don't like the form? That's ok, just email us. Thank you.
Interested in working together? Just fill out the form below. Don't like the form? That's ok, just email us. Thank you.
Interested in working together? Just fill out the form below. Don't like the form? That's ok, just email us. Thank you.
THE 5TH WORLD LAUREATE FORUM
AND OTHER EVENTS PARTICIPATED
SAM QIAN
How do I Prepare for Robotics Competitions?
From Blueprint to Battle: The Birth of Our Robot
When I first heard about the FIRST Robotics Competition, I had no idea how much it would change the way I see teamwork, creativity, and problem-solving. At Yew Wah School of Shanghai, we had a small but passionate robotics team. We weren’t the biggest or the most well-funded, but we had something powerful, a shared dream of building something that could move, think, and compete.
Our journey started with a blank page, literally. On our first day of preparation, we gathered around a whiteboard and started throwing out ideas for our robot. The challenge theme that year was intense, requiring both precision and speed. We knew that to stand out, we had to create a robot that could not only complete tasks efficiently but also adapt to unpredictable conditions.
The early brainstorming sessions were chaos, in a good way. One of us wanted a high-torque arm, another argued for faster wheels, and someone else said, “Let’s teach it to think.” That’s when the idea of integrating AI algorithms came up. I remember the excitement in the room, the kind where everyone starts talking over each other, sketching wild ideas, and pulling out laptops to test theories.
We started drawing rough blueprints on the whiteboard, it looked like a cross between a spaceship and a lawnmower. But that’s the beauty of building something from scratch: you don’t know what it will become, but you keep improving it every day.
Our first prototype barely moved. It was clunky, heavy, and one of the motors overheated during testing. But instead of feeling discouraged, we laughed about it. Every failure became a funny story and a lesson. We’d fix one issue and discover three more. Slowly, though, the robot began to take shape — from messy sketches to a moving machine that responded to our code.
The moment our robot completed its first smooth turn, we all cheered. It wasn’t perfect, but it worked. We named it — every team has to, right? It became part of our identity. To us, it wasn’t just metal and wires; it was a piece of our collective effort and creativity.
Our lab often turned into a battlefield of ideas and cables. Late nights, takeout boxes, and half-empty energy drink cans became the background of our preparation. Every bolt tightened, every circuit connected, and every test run brought us closer to something that felt alive. By the end of the build phase, we had a robot we were genuinely proud of — one that represented teamwork, innovation, and countless hours of dedication.
Coding the Brain: Teaching Our Robot to Think
Once the robot’s body was built, it was time to give it a brain. This was my favorite part — programming. I’ve always believed that code is like magic: invisible lines of logic that bring cold metal to life.
Our goal was ambitious — to make the robot smart. Not just remote-controlled, but capable of reacting intelligently during the match. That’s where my role as the AI programmer came in.
I started by writing simple movement functions — forward, backward, rotate, grab. Those were easy enough. But as we advanced, the codebase grew huge. We had to integrate sensors, cameras, and motion detection algorithms. Our robot needed to “see” and “decide” in real-time, especially during the autonomous phase of the competition, when no human control is allowed.
There were moments of real frustration. Sometimes the robot wouldn’t follow commands; sometimes it spun in circles for no reason. We had bugs that refused to die. But the best moments came after hours of debugging when suddenly — everything worked. Watching our robot move accurately based on its sensor input felt like witnessing a small miracle.
The core of our success came from an AI-based path optimization algorithm I helped write. It allowed our robot to analyze the shortest route between two points while avoiding obstacles. It wasn’t something we copied — it was something we designed through trial, error, and intuition.
That’s the thing about robotics: it’s a mix of logic and creativity. You can spend hours on math, and yet one small tweak — one new idea — can completely change performance.
I remember one weekend when we stayed up till midnight trying to improve our robot’s precision. The sensors kept giving inconsistent readings. Someone suggested covering the floor with white tape to improve contrast, and suddenly, everything worked better. It was a small fix, but it reminded me how innovation often comes from observation and teamwork, not just theory.
We spent weeks testing, improving, and rewriting code. Each line of code became a memory of effort and teamwork. When the robot finally started performing consistently, we knew it was ready to take on the world.
Teamwork in Action: Late Nights, Laughter, and Lessons
Behind every successful robot is a team of tired but passionate students. We all had different strengths — some loved coding, others were amazing with mechanical designs or 3D printing, and some just had incredible problem-solving instincts.
Teamwork wasn’t always easy. We argued, disagreed, and occasionally broke things (both physically and emotionally). But every challenge taught us how to communicate better. We learned to listen — really listen — to each other’s ideas.
I still remember one of our biggest disagreements — about whether to prioritize speed or strength. Half the team wanted lighter materials; the other half wanted stronger arms for gripping. We ended up doing a hybrid design, combining aluminum and reinforced plastic. It turned out to be the best decision we could’ve made.
There were also countless fun moments. We celebrated small wins with pizza and silly dances. We gave each part of the robot a nickname — the claw was “Hungry,” the drive system was “Bolt,” and the sensor unit became “The Eye.” It might sound childish, but that sense of humor kept our energy up through long nights.
Our workspace was a mess — wires everywhere, sticky notes on the wall, whiteboards full of formulas and doodles. It looked chaotic, but it was our creative space. Every corner held a story — like the day we dropped a motor and it stopped working, or when our teacher caught us blasting music during testing.
But most importantly, we learned the meaning of trust. In robotics, one person’s mistake can crash the whole system, but one person’s breakthrough can lift the entire team. We depended on each other. When I saw how each teammate grew — becoming more confident, more skilled, and more passionate — I realized that robotics isn’t just about machines. It’s about people learning how to collaborate and innovate together.
Road to the Arena: Preparing for the Big Stage
The weeks before the competition were some of the most intense — and exciting — days of my life. We’d worked for months, and now it was time to test everything under real competition pressure.
We started with mock matches at school. The first few were disastrous. The robot froze mid-match, a wheel came loose, and our arm failed to grab an object properly. But every failure made us sharper. We began keeping a detailed troubleshooting log, listing every issue and its fix. Slowly, the problems disappeared.
Our teachers and mentors were incredibly supportive. They helped us with logistics, sponsorships, and guidance. When we finally received confirmation to represent Yew Wah School of Shanghai at the international level, the room exploded in cheers.
Packing for the trip felt surreal. We labeled every wire, packed extra batteries, screws, and backup tools. It felt like we were preparing for a mission to Mars.
When we arrived at the competition venue, the energy was unbelievable. Teams from all around the world had gathered — each with unique designs, flags, and team chants. You could feel the spirit of innovation in the air. Everyone was friendly but also fiercely competitive.
The first time we saw our robot on the field, my heart raced. As the driver, I felt the pressure — every move mattered. During our first match, our robot performed almost flawlessly, hitting targets with precision.
Standing there, watching our robot perform in front of an international audience, I felt a mix of pride, relief, and disbelief. All the late nights, the arguments, the small victories — they all led to that moment.
We didn’t just build a robot. We built something that represented our creativity, resilience, and teamwork. The applause, the friendships, and the memories — those were the real prizes.
Preparing for the FIRST Robotics Competition was more than a school project — it was an unforgettable adventure. From our first sketches to the international stage, every step taught me something new about technology, teamwork, and perseverance.
If you’re reading this and thinking about joining a robotics team — do it. You don’t have to be a tech genius. You just need curiosity, a bit of courage, and a team willing to dream big. Because in the end, robotics isn’t just about robots — it’s about people building the future, one idea at a time.