What Feedback Taught Me About Growth by Yusuf

What Feedback Taught Me About Growth by Yusuf - August 2026 Scholarship Essay

Feedback used to feel like a verdict. My first semester as a computer science major, a professor handed back a project with more red ink than I had seen since elementary school, and my instinct was to explain it away: I was juggling a research lab, a tutoring job, and a treasurer role, so of course something had to give. It took a second, gentler but more direct conversation with a teaching assistant to make me actually hear what the feedback was telling me, which was not "you are failing" but "you are trying to do too much at once without a system."

That distinction changed how I approach almost everything now. Instead of treating a low grade or a rejected pull request as a referendum on my ability, I have trained myself to ask a narrower question: what specifically broke, and what would I need to change to fix just that? When my code review comments kept flagging the same category of bug, I stopped assuming I needed to "be more careful" and instead built a personal checklist before every commit. When my research advisor pointed out that a paper draft buried its contribution in the fourth paragraph, I did not take it as a comment on my writing ability in general; I learned to write my conclusion first and build backward from it.

This habit mattered most while building LoadLink, a tool I developed over a summer internship to help freight carriers and dispatch staff stop retyping the same load information three times into three different systems. My first version of the parser was too rigid; it choked whenever a trucker's WhatsApp message did not match the format I expected. Watching it fail in front of the ops team was uncomfortable, but their reaction was useful feedback, not criticism: they needed something that degraded gracefully. I rebuilt the tool with a small local model doing the first pass and a regex fallback catching what the model was not confident about, and that redesign came directly from watching people struggle with version one.

I still carry the lower GPA from that overloaded semester, and I am not going to pretend it does not matter. But learning to separate feedback about a specific decision from feedback about my worth is the reason my study habits, my code, and my research writing have all improved since. I used to hear "here is what needs to change" as "you are not good enough." Now I hear it as the fastest way to get better, and I go looking for it instead of avoiding it.