I became interested in computer science because I was fascinated by the idea that a few lines of code could solve real problems and help people learn and grow. Coming from Azerbaijan, I did not grow up surrounded by advanced technology opportunities or extensive computer science programs. When I started studying computer science at Santa Barbara City College, I often felt behind classmates who already had years of programming experience. However, that challenge motivated me to work harder and improve my skills instead of giving up. One experience that strengthened my interest in computer science happened during my C++ course at Santa Barbara City College. Two weeks before the semester began, the class switched from in-person lectures to a fully self-paced format. Although recorded lectures and materials were still provided, many students struggled because this was their first experience with programming. Without live instruction or immediate feedback, assignments that were already difficult became even more overwhelming. I understood that frustration because I had experienced it myself throughout the semester. Near the end of the course, I decided I wanted to improve the experience for future students. I helped redesign the homework system by creating ten new programming assignments focused on functions, arrays, pointers, classes, and debugging. Instead of traditional textbook exercises, I designed projects that were more interactive and engaging. Some assignments became mini systems or games, including “RectoWars,” which focused on collision detection, and a Playlist Manager that taught object-oriented programming and dynamic memory management. I also developed automated unit tests using Google Test and CMake so students could receive immediate feedback on their code. Creating those tests became the most difficult part of the project because real students make unpredictable mistakes. I spent hours debugging edge cases, rewriting test cases, and improving feedback so students could better understand what went wrong in their programs. A few months later, the professor told me students were completing projects more independently and asking fewer repetitive questions because the tests and documentation helped guide them through debugging. The moment that stayed with me most was seeing another student in the computer lab repeatedly run the Playlist Manager tests, fix his code, and continue improving without asking for help. Watching that process made me realize that technology can do more than solve technical problems; it can also build confidence and create learning opportunities for others. My goal after earning my degree is to become a software engineer and continue building technology that helps people solve problems and access opportunities. I believe I am a strong candidate for this scholarship because I have consistently worked to improve myself despite limited early access to computer science resources, and I try to use my skills not only to grow personally but also to help others learn and succeed.

My C++ class at Santa Barbara City College switched from in-person lectures to a fully self-paced format two weeks before the semester began. Although our instructor still uploaded recorded lectures and materials, many students struggled because this was their first experience with programming. Without live instruction or immediate feedback, assignments that were already difficult became even more overwhelming. I understood that frustration personally because I had experienced it throughout the semester myself. Near the end of the course, I realized I could either finish finals and move on or try to improve the experience for future students. I decided to help redesign the homework system for the next semester. It was not for extra credit or payment. I simply wanted to contribute something useful to a class that many students found intimidating. I started by identifying the topics students struggled with most: functions, arrays, pointers, classes, and debugging. Instead of traditional textbook exercises, I created ten programming assignments designed to make the course more interactive and engaging. I wanted the projects to feel creative rather than repetitive, so many became small systems or games. One assignment, “RectoWars,” focused on object movement and collision detection. Another project was a Playlist Manager where students practiced object-oriented programming and dynamic memory management by adding, removing, and organizing songs. I also created a Smart Home Simulator where virtual devices interacted through classes and functions. For every project, I wrote detailed README files explaining the requirements and suggested approaches. I tried to explain concepts the way I wished they had been explained to me when I first started learning programming. I remembered spending hours staring at compiler errors and questioning whether I truly belonged in computer science. The most challenging part of the project was developing automated unit tests using Google Test and CMake. I wanted students to receive immediate feedback on their code instead of waiting for office hours or manual grading. The tests automatically checked outputs, memory handling, invalid input cases, and edge cases. Creating those tests became far more difficult than I expected. Real students make unpredictable mistakes. Some programs crashed with empty input, while others failed because of memory or formatting issues. I spent hours debugging the testing framework itself and rewriting test cases so the feedback would accurately help students understand what went wrong. A few months later, I returned to ask the professor how the assignments were working. She told me students were completing projects more independently and asking fewer repetitive questions because the tests and documentation helped guide them through debugging. The moment that stayed with me most happened the following semester when I walked into the computer lab and saw one of my Playlist Manager assignments open on another student’s laptop. He kept running the tests, watching them fail, fixing his code, and running them again. Every time another test passed, he quietly moved on to the next issue without asking for help. Watching that process made me realize the system was accomplishing exactly what I hoped it would do. That experience changed the way I view technology. I realized computer science is not only about writing code, but also about creating opportunities for others to learn, grow, and gain confidence in skills that once felt impossible.