Learning to Explain the Work Clearly by Aayush
Aayush's entry into Varsity Tutor's November 2026 scholarship contest
- Rank: 58
- 0 Votes
Learning to Explain the Work Clearly by Aayush - November 2026 Scholarship Essay
The academic skill I want to develop further is communication — not talking more, but explaining technical work clearly enough that someone outside the project can follow it and use it.
I noticed the gap while working on DeepInvent last summer. I spent May through August 2026 building part of an agent core that reproduces machine learning papers from an arXiv ID and runs across multiple clouds on GPUs. The code worked, but when I tried to describe what it did, I either left out steps that mattered or buried the main point in details. The same thing happened in the UT Learning-Directed OS Lab, where I worked with ROS 2 and LTTng from December 2024 to May 2026. I could trace what the system was doing, but turning that trace into a short, clear explanation took much longer than the debugging itself.
MyFutureSelf made the point harder to ignore. As an iOS intern from July to October 2025, I helped build an app in SwiftUI with Firebase that went from zero to more than 5,000 users. Users do not read code. They read a screen, a message, or a short explanation, and if that explanation is unclear, the feature might as well not exist. With OpenApplier, which now has more than 500 users, I ran into the same thing: the value of the tool depends on whether a new person can understand in a minute what it does and why it helps them.
So I want to get better at writing and talking about work in that order: what the problem is, what I tried, what happened, and what is still missing. I am practicing by writing shorter summaries of what I build, cutting sentences that only sound technical, and asking whether a reader who has not seen the project would still follow it.
That skill supports what I want to do next. I am studying computer science and mathematics at UT Austin, and I plan to keep building software that other people actually use, including during my upcoming internship at Shopify in early 2027. The work will involve other engineers, designers, and users, and most of the decisions will be made through written explanations and short discussions, not through code alone. If I can explain a system plainly, I can get better feedback, catch mistakes earlier, and hand work off without it breaking in translation. That is the part I want to keep improving.