Vice-Captain and Control Systems Lead on Team IK19859. I write the autonomous code — Java, PID loops, sensor fusion — that makes the robot think for itself in a 30-second window.
That means debugging at 11 PM before a match when code that worked in practice won't initialise on the competition field. The real skill isn't writing — it's rewriting under pressure.
Before FTC, I competed in WRO and FLL in 5th and 6th grade — that's where the obsession with robotics started.
"The robot doesn't know you're nervous. The code either works or it doesn't."
I also run strategy and scouting — reading opponent alliances, calling configuration changes between matches. Engineering and strategy are inseparable at this level.
Beyond competition, I designed and built 19859.org — the team's official bilingual website — as part of the sponsorship and outreach side of the role. It covers the robot, season, software, and community across English and Chinese.
30 seconds. Zero human input. Everything below has to work in concert — or the robot's dead on the field.
The stack in Chapter 2 powers the robot. I also built the intelligence layer our team uses for alliance selection — a full-stack platform used in real competition.
scoutselect.org Full write-up & interactive demoDidn't make it past qualifiers our first season. This season, we qualified for Worlds in Turkey. Four seasons of getting better.
IK19859 · 2025 Competition Robot
Istanbul, July 2026. Teams from every continent. Six years of work leads here.
Three design awards, two champion alliances, a China Nationals finalist run. We earned this across an entire season — not one lucky weekend.
The same precision that makes a 98%-consistent autonomous routine works in water too. World #6. Six medals in one season.
Control Systems Lead and Team Champion — different arenas, same core skill: build the argument, test it under pressure, iterate.
Built because competition demanded it. OPR, Monte Carlo, Bayesian shrinkage — running on live FTC data at California Invitational.