This is the required supplement for Yale. It's just an essay about something that I like, and I want to bring that to the Yale community.
Pokémon. The first thought that comes to mind is that childish game almost every kid loved. It was, and still is, a game that involves strategy and prediction, like online Risk. With 8-bit music and 150 critters, there was every reason to love it. As we learned calculus, built computers, and exhausted our bodies through sports, we forget those small trinkets our lives formerly revolved around. However, Pokémon has grown with us.
As the senior strategy analyst at Thunder Fusion, I construct teams for the sole purpose of competitive battling. The new damage formulas are available for a reason. To most players, it is nothing more than another math problem that shouldn't be in something fun. To me, it is the Holy Grail. That Holy Grail brought me to 11th in the International Pokémon Tournament.
Engineering a Pokémon team is like designing a computer, except with only six parts. The first step is to analyze the objectives. Pure offensive team. High speed, low power. The objectives then provide a goal for research, a strategy or theme to follow. High speed, attack, and special attack stats. Fast processor, efficient power supply. I run diagnostics on how effective it will be and predict the expected performance. Next, I identify synergy between different members of the team, creating the mainframe of the team. The remaining parts give added flexibility, to address common problems. Threats: Azelf, Infernape, Scizor. Hazards: humidity, dust, electric shock. Not only do major issues need to be recognized, I also have to take steps in addressing them. Like how good ventilation prevents a computer from overheating, a proper defensive wall suffices against several threats.
Before I release the team, it must run through a battery of tests. I check its performance, debug any obvious flaws, and examine its use in the long term. This is also when I fine-tune the stats values. This labor-intensive process utilizes my Holy Grail by calculating how many points Cresselia requires to switch in, take two attacks at maximum damage, and defeat it with Psychic. The same process takes place in making sure a computer has just enough resources to allow it to perform its job.
All of these steps are critical to engineering, whether it be something as trivial as a Pokémon team or something as significant as the next generation computer. Even after they are built, they require care and maintenance to stay fully operational. Pokémon teams need to adapt to strategy alterations, or they are dismantled easily. Computer users must similarly update their software protection to prevent viruses and other malware from infecting their computers.
Through Pokémon, I developed a natural methodology for project management. The more I played, the more I realized how many of the skills in becoming a good battler are nearly identical to those of an engineer. I love having challenges to overcome, discoveries to make, and friends to meet. I love to analyze others and myself. I love logical planning. I love Pokémon.
Please be harsh. Thank you. I'll try to return the favor :)