mitadmissions.org/blogs/entry/is-mit-too-hard
I used to think that MIT was unnecessarily hard. Certainly it feels that way in the middle of a hell week - what's the point of having midterms, psets, and essays clustered in the same few days, anyway?
And you know what? MIT is unnecessarily hard -- at least if you think the purpose of school is to "teach you material." Tight, clustered deadlines don't make you learn material any better. Turning in a pset 24 hours late doesn't mean that you have a lesser understanding of the subject.
But now that I'm here working in the Real World™ (sort of), I've learned to appreciate the frantic pace of MIT - the sense of urgency for urgency's sake. Like the marathoner's training, it builds up your base endurance, your tolerance for discomfort. It sucks in the moment, but lets you do cool things. And it means that when something is actually urgent, you're prepared.
After all, when Tim Cook wants something on his desk in three hours, punting is not an option.
--
Last week, I worked 75 hours -- which, well, in itself is not something to be proud of. As my friend Steph C. '15 sardonically put it, "Congratulations on being a professional workaholic."
But what I am proud of, is the fact that I've managed to put in these hours while also (1) getting the most sleep I've ever gotten, (2) eating the healthiest I've ever eaten, and (3) exercising the most I've ever exercised. And the reward? Getting to work on and take some ownership of the coolest projects I've ever seen.
Without the rigor of MIT, I don't think the transition would have been so smooth.
In the end, people who tell you that life is a marathon, not a sprint, are correct. One way to respond to that statement is to slow down. Another way is to train so hard that your marathon pace is someone else's sprint pace.
That's how you pull away from the pack.