A student redesigns access to an evening coding course when transportation makes attendance unequal.
The free coding course met at 6:30 p.m., forty minutes after the last direct bus left my neighborhood. I attended by taking two routes and walking from a transfer stop, but three classmates disappeared after the first week. The program called the course open-access because tuition was zero. Transportation, dinner schedules, and family responsibilities were costs the registration page did not count.
I asked the instructor to record lectures, but classmates explained that video alone would not replace debugging help. We created a hybrid lab on Saturday afternoons at the library. I reserved laptops, converted exercises to run without software installation, and paired remote students with in-person partners through a shared error log. The first log was chaotic, so we added fields for expected output, attempted fixes, and the smallest reproducible example. Students who missed Tuesday could arrive Saturday with a problem others could actually investigate.
The opportunity taught me coding, especially the patience required to isolate an error. Building access to it taught me something broader: an open door is not an accessible path. I learned to identify which part of an experience cannot simply be recorded—the conversation, equipment, feedback, or protected time—and design around that missing function. I still took the long bus route when I could. The difference was that learning no longer depended on everyone having the same route, and our debugging practice improved for every student because we documented exactly how we got stuck instead of hiding it from one another during the weekly lab.
Original teaching sample written by the Writivia team. It is not a real student's submitted essay and does not imply admission to University of California, Los Angeles.