College Essay Editor - Admission Essay Editing and Review Service

Common App main essay - draft, 912 words

Ever since I was young, I have been fascinated by how systems work, whether in nature, in machines, or in the everyday routines that keep a small business running. This particular fascination has shaped who I am today in ways I am only now starting to understand, and it has guided many of the choices I have made, including my decision to study computer science in college. Nowhere has this been clearer to me, in a real and lasting way, than at my family's small bakery, where I have spent nearly every Saturday of my adolescence, quietly learning things that no classroom could ever really teach me about precision, trust, and the persistent gap between what people say they did and what actually, verifiably happened.

Nazir's Bakery is a twenty-two-seat shop my parents opened twelve years ago with one mixer and a folding table. Every Saturday since I was eleven, I have woken at 5:30 a.m. to help open it. My job used to be simple: wipe the display case, count the register drawer, stack the paper bags into neat towers by the register so my mother would not have to stop and search for one mid-order. When I was fourteen, my father handed me something heavier: a clipboard hanging inside the walk-in cooler door, where someone was supposed to record the internal temperature every two hours, so that if a health inspector ever asked, we would have proof that nothing had crept above 41 degrees during a shift.

For the first few months I copied the same number my father had written the previous hour, because walking to the cooler in the middle of a Saturday rush felt like a waste of thirty seconds we did not have. Then, in March of my sophomore year, I read six weeks of entries in a row and noticed the numbers rose and fell in a pattern that had nothing to do with the compressor and everything to do with whoever happened to be holding the pen. My father's readings clustered near 36. Mine clustered near 39. Neither of us was lying to the log. We were both guessing, and guessing at different temperatures, and neither of us had ever said so out loud.

The cost of that guessing became clear one Sunday in April, when we threw out forty dollars of pastry cream because nobody could say whether it had spent six minutes or six hours above forty-five degrees before someone noticed the door propped open by a delivery cart. My father blamed the delivery driver. I checked the log first and found the entry for that hour in my own handwriting, copied from the hour before, the way I always copied it when the rush was on. I did not tell him that part until months later, after the spreadsheet existed and the blaming had somewhere better to go than a person's memory of a Sunday that had already happened.

I asked my father if I could replace the clipboard with something that measured instead of guessed. He said the clipboard was free and a thermometer was not, which was a fair answer from a man who had opened a bakery with a single mixer and a folding table. I spent four Saturdays' worth of tips on a thirty-eight-dollar wireless probe thermometer and built a spreadsheet that logged the reading automatically every fifteen minutes, then flagged any hour where the average drifted more than two degrees outside the thirty-six-to-thirty-eight range we needed. I did not know what a script was yet. I just wanted the numbers to stop lying to us, and to stop being able to lie to each other by accident.

The spreadsheet caught its first real problem that October: a door seal failing slowly enough that no single two-hour reading looked wrong, but the six-hour trend line did. We replaced the forty-dollar seal before it became a four-thousand-dollar compressor. My father started asking me to check "the numbers" before he asked about anything else on a Saturday morning, which is the closest he has come to admitting that his fourteen-year-old daughter's spreadsheet noticed something his memory could not.

What I learned in that cooler was not really about refrigeration. It was that a system only tells the truth if you build it to catch the ways people are naturally sloppy: tired, rushed, thirty seconds short on a Saturday morning. That is the same problem I now chase in the introductory programming class I take at the community college near my high school, where the interesting part is never getting the code to run once, but getting it to keep telling the truth on the tenth run, the hundredth, the one nobody happens to be watching. I still open the bakery most Saturdays. I still check the spreadsheet before I check my phone. But I understand now that the clipboard itself was never really the problem. The thirty seconds we did not think we had was, and it still is, in every system I have built since.

College is where I want to keep learning how to build systems that hold up under the same kind of real-world pressure: the pressure of real people, on real mornings, who are genuinely doing their very best but are, in the end, only human, which is something I find myself thinking about every single time I walk past that cooler door on my way to open the register for another long Saturday shift.

Margin noteNote (structural edit): restates, in the abstract, what paragraph six already shows in a scene. Flagged for removal; the idea survives, folded into the reflection below. Note (line edit): "in a real and lasting way," "quietly," "particular," "actually, verifiably" are hedges. Cutting them does not change the meaning.

Margin noteNote (structural edit): the strongest scene in the draft and it arrives third. It should be closer to the opening.

Margin noteNote (line edit): the closing sentence is 74 words and ends on an abstraction ("only human") instead of an image. Pass three rewrites it.

Common App main essay - submitted, 648 words

Nazir's Bakery is a twenty-two-seat shop my parents opened twelve years ago with one mixer and a folding table. Every Saturday since I was eleven, I have woken at 5:30 a.m. to help open it. My job used to be simple: wipe the display case, count the register drawer, stack the paper bags. When I was fourteen, my father handed me something heavier: a clipboard inside the walk-in cooler door, where someone recorded the internal temperature every two hours, so that if a health inspector ever asked, we would have proof nothing had crept above 41 degrees during a shift.

For the first few months I copied the number my father had written the previous hour, because walking to the cooler mid-rush felt like thirty seconds we did not have. Then, in March of sophomore year, I read six weeks of entries in a row and noticed the numbers rose and fell in a pattern that had nothing to do with the compressor and everything to do with whoever was holding the pen. My father's readings clustered near 36. Mine clustered near 39. Neither of us was actually lying. We were both guessing, at different temperatures, and neither of us had said so out loud.

The cost of that guessing became clear one Sunday, when we threw out forty dollars of pastry cream because nobody could say whether it had spent six minutes or six hours above forty-five degrees before someone noticed the door propped open. My father immediately blamed the delivery driver for it. I checked the log first and found that hour's entry in my own handwriting, copied from the hour before, the way I always copied it when the rush was on. I did not tell him that part until months later, after the spreadsheet existed and the blame had somewhere better to go than a memory.

I asked my father if I could replace the clipboard with something that measured instead of guessed. He said the clipboard was free and a thermometer was not, a fair answer from a man who had opened a bakery with a single mixer. I spent four Saturdays' tips on a thirty-eight-dollar wireless probe thermometer and built a spreadsheet that logged the reading every fifteen minutes, then flagged any hour where the average drifted more than two degrees outside the range we needed. I did not know what a script was yet. I just wanted the numbers to stop lying to us.

The spreadsheet caught its first real problem that October: a door seal failing slowly enough that no single reading looked wrong, but the six-hour trend line did. We replaced the forty-dollar seal before it became a four-thousand-dollar compressor. My father started asking me to check "the numbers" before he asked about anything else on a Saturday morning, which is the closest he has come to admitting his daughter's spreadsheet noticed something his memory could not.

What I learned in that cooler was not really about refrigeration. It was that a system only tells the truth if you build it to catch the ways people are naturally sloppy: tired, rushed, thirty seconds short on a Saturday morning. That is the same problem I now chase in the introductory programming class I take at the community college near my high school, where the interesting part is never getting code to run once, but getting it to keep telling the truth on the tenth run, the hundredth run, the one nobody happens to be watching that Saturday morning. I still check the spreadsheet before I check my phone.

College is where I want to keep learning how to build systems that hold up under the pressure of real people, on real mornings, doing their best but only human — the exact kind of pressure a clipboard cannot survive, and a spreadsheet, checked honestly by someone willing to read it, can.