More Than a Finished Screen
1Our school should offer an introductory coding class. I used to picture coding as a race to make something impressive flash across a screen. Then a lunchtime workshop left me staring at a blank square, learning something I had not expected. The square was supposed to become a button that would display a welcome message.
2At first, I copied the workshop leader's example without pausing. Around me, students were choosing colors and changing fonts. I chose bright orange, certain that mine would be easy to spot. When I clicked my button, nothing happened. I clicked harder, as if the computer could measure how badly I wanted a response.
3My partner, Hyejin, slid her chair closer. The workshop leader was helping another table. “Tell me what you expected,” Hyejin said. Her notebook lay open beside the keyboard. I reached for the mouse, then stopped. “A message should appear,” I said. “But I don't know which instruction makes that happen.” Saying it aloud was worse than seeing the empty square.
4We read the instructions one line at a time. “This name has an extra letter,” Hyejin said, pointing between the screen and the example. I deleted it. Before clicking again, I traced the two names with my finger: one in the button's label, one in the instruction connected to it. This time, the welcome message appeared. My shoulders dropped. We had changed one letter, but I finally understood what we had changed.
5A few minutes later, Hyejin's button failed. I almost pointed straight at the line I thought was wrong. Instead, I asked what she expected to happen. She described the steps, found a missing connection, and fixed it herself. We spent the remaining minutes testing each other's buttons, deliberately trying choices we had not tried before.
6A single workshop did not turn us into experts. It did give us time to make a mistake, explain it, and try again. A coding class could make room for more of that work. My orange button was not the most polished project in the room. When I left, though, I could explain why it worked.