Every build has a story.

Our robot is no longer just a collection of individual parts. We brought the drivetrain, electronics, wiring, frame, and early mechanisms together into one working platform.

This milestone taught us that integration is where engineering gets real. Every bracket affects another component, every wire needs a safe route, and every mechanism must remain accessible for testing and repair.

We learned to prototype before committing to a permanent mechanism. Cardboard, temporary supports, loose positioning, measurements, and quick fit checks helped us answer important questions early.

Instead of hiding failed attempts, we treat them as evidence. A part that does not align, a mechanism that binds, or a layout that is hard to service gives us the information needed for the next version.

Our programming journey began with the fundamentals: setting up the development environment, understanding the FTC SDK, using Git and GitHub, creating branches, and learning how code reaches the robot.

We are building habits that will matter later—small changes, readable code, meaningful commits, peer review, and testing one behavior at a time. The goal is not only to make the robot move; it is to understand why it moved and to reproduce that result reliably.

Our first major build milestone was simple but meaningful: creating a square, stable aluminum frame together. It gave us our first real look at how measurements, fasteners, alignment, and teamwork affect a robot.

More importantly, this was the moment the project became ours. We could hold something we had planned and assembled together—and imagine all the systems that would eventually grow from it.