Exams and Assignments: The Final Stretch

Exams and Assignments: The Final Stretch

There is a particular kind of pressure that builds up in the last few weeks of a semester, and this term it arrived almost all at once. Assignments that had been sitting comfortably on a to-do list for weeks suddenly all had deadlines within days of each other, and quizzes in Digital Logic Design, Database Systems, and Object-Oriented Programming landed in the same short stretch of time as well. I had known these dates were coming since the start of the semester, but knowing a deadline exists and actually feeling its weight turned out to be two very different things.

Mornings during that stretch started earlier than usual, and the day rarely slowed down enough to leave room for much beyond moving from one task to the next. Meals got skipped more often than they should have, not out of any plan but simply because sitting down to eat felt like time I could not spare. Looking back, that was probably one of the clearest signs that my time management earlier in the semester had not been as good as it needed to be a well-prepared version of that week would not have required skipping meals to get through it.

The assignments themselves were not uniformly difficult; some were straightforward continuations of lab work I had already mostly understood. The real difficulty was volume and timing three or four moderately demanding tasks converging on the same few days, with very little slack to absorb anything going wrong. A small bug in a Database Systems assignment that would normally take twenty minutes to fix instead ate into time that I had mentally already allocated to studying for a Digital Logic Design quiz the next morning. Every delay had a ripple effect on everything scheduled after it.

Quizzes added a different flavor of pressure, since they could not be pushed back or worked through gradually the way an assignment could. A quiz forces a kind of preparation that has to happen in advance, in a fixed window, with no opportunity to figure things out as you go the way you sometimes can with a longer assignment. Preparing for the Digital Logic Design quiz while simultaneously trying to finish a pending Database Systems assignment meant my attention was constantly split, and I do not think I gave either task the full focus it deserved during that week.

What got me through it, more than any single study technique, was accepting that the week would simply be uncomfortable and choosing to move through it one task at a time rather than trying to mentally hold the entire pile of pending work at once. Each assignment finished, each quiz attempted, felt like a small relief, even while the next item on the list was already waiting. There was very little satisfaction in any individual task during that stretch the satisfaction came only once the entire backlog had finally cleared.

The lesson from this part of the semester is one I had technically already learned and apparently still needed to relearn the hard way: preparing earlier, even a little, compresses the panic at the end dramatically. A quiz studied for gradually over two weeks feels completely different from the same quiz crammed into one exhausted evening, even if the final grade ends up similar. The difference is not really about the outcome it is about how much of the semester gets spent stressed versus how much gets spent actually absorbing the material with some room to think.

Going into the next semester, the plan is simple to state and, I know from experience, harder to actually follow: start assignments the week they are given rather than the week they are due, and treat quiz preparation as something that happens gradually across several days rather than in a single late-night push. Whether I actually manage to follow that plan consistently is something only the next set of exams will tell.

One specific moment from that week stands out clearly. I had a Database Systems assignment due the same morning as a Digital Logic Design quiz, and I made the decision, somewhat reluctantly, to finish the assignment first and study for the quiz on almost no preparation beyond a quick glance at my notes during breakfast. The assignment turned out fine, but the quiz did not go nearly as well as it should have, given how comfortable I actually was with the material once I had time to think about it properly afterward. That single trade-off, made under pressure with too little sleep to think clearly about which choice was actually better, taught me more about prioritization under stress than any calm planning session ever could have.

Looking at the pile of assignments after that week was finally over, I noticed something that should have been obvious earlier but only became clear in hindsight: very few of them were individually difficult. Most required maybe two or three focused hours of work, work I had genuinely done dozens of times before in other contexts throughout the semester. What made them feel overwhelming was never the content, it was the number of them landing at once with no buffer between any two deadlines. That distinction matters, because it means the fix is not really about getting better at the subject material I already understood most of it reasonably well but about distributing the same amount of work across more days instead of letting it all collapse into the same few.

Quizzes specifically left me thinking about how differently I study for something with a fixed, unmovable time slot compared to something with a flexible deadline I can quietly push back in my own head. An assignment due “by midnight” has a way of slipping to 11:58 PM almost by habit. A quiz at a specific time the next morning does not offer that same flexibility, and recognizing that difference made me realize quizzes deserve dedicated study sessions placed deliberately on the calendar in advance, rather than being squeezed into whatever leftover time happens to exist after assignments are finished.

By the time grades for that period eventually came back, most of them were reasonable, which was honestly a relief given how stressed the week itself had felt. But I do not think a reasonable grade should be mistaken for evidence that the approach was fine. The process behind that week skipped meals, late nights, last-minute studying is not something I want to repeat as a strategy, even if the outcome happened to be acceptable this time. Next semester, the goal is not just better grades, but a calmer, more sustainable path to getting there.

In hindsight, I also notice how much of the stress during that final stretch came from uncertainty rather than from the actual difficulty of any single task. I did not always know exactly how much time a remaining assignment would take, which made it hard to plan the rest of the day around it with any confidence. A task that turned out to take twenty minutes felt just as worrying beforehand as one that ended up taking two hours, simply because I had not estimated either one accurately. Learning to make even a rough time estimate before starting something, instead of diving in blind, is a small habit I want to build more deliberately, since it would have made that entire week feel less chaotic even if the actual workload had stayed exactly the same.

I also want to be honest that not every assignment from that period reflects my best work, and I think that is worth admitting rather than glossing over. A couple of submissions were finished mainly to meet the deadline rather than because I felt genuinely satisfied with the result. That is a real cost of poor earlier planning, not just a hypothetical one it shows up directly in the quality of work produced under unnecessary time pressure. Recognizing that cost clearly, rather than only feeling vaguely guilty about it, is part of what makes me actually want to change the pattern next semester instead of just hoping it goes better by chance.