Compiler Design Is Testing My Patience

Sunday was productive, but honestly, it was also exhausting.

I continued with Compiler Design and completed Lectures 7, 8, and 9. I also finished the pending notes for Lectures 5 and 6, so at least that backlog is cleared.

However, the parsing concepts are becoming increasingly difficult to follow, and the lecture lengths are starting to test my patience.

With October 31 approaching, I am beginning to think more seriously about how I should balance completing the syllabus with actually understanding what I study.

Three Long Lectures of Compiler Design

My Sunday started with some pending work from the previous day. I completed the notes for Compiler Design Lectures 5 and 6 before continuing with the next lectures.

After that, I completed Lectures 7, 8, and 9.

Each lecture was approximately 2.5 hours long.

Yes, each one.

By the time I had worked through all three, it felt like I had spent the day attending a Compiler Design marathon. The difference was that I couldn't even claim a medal at the finish line.

Still, I completed the entire lecture content. I didn't skip the difficult explanations just because they were taking time.

That was the productive part of the day. The difficult part was understanding everything that came toward the end.

LL(1), LR(0), SLR and CLR: Things Started Getting Complicated

The lectures covered parsing methods such as LL(1), LR(0), SLR(1), and CLR(1).

Initially, things were manageable. LL(1) and LR(0) felt understandable, and I could follow the explanations.

The difficulty increased when we moved toward SLR and CLR.

We weren't constructing parsing tables in these lectures. Instead, we were drawing DFAs, identifying states, and checking whether conflicts existed. Then the professor started explaining the relationships between the different parsing methods and grammar classes.

That was the point where things started going over my head.

It wasn't just about understanding one algorithm anymore. I was trying to keep track of several methods, their differences, the DFA states, possible conflicts, and the relationships between them.

I could follow parts of the explanation, but putting everything together was becoming difficult.

I don't know whether the main problem was that I was trying to absorb too many concepts at once or that the professor was going into more depth than I could comfortably process during my first pass.

Probably, I need to revisit these concepts more systematically instead of expecting everything to click immediately.

Difficult Questions Versus Efficient GATE Preparation

One thing worth mentioning is that the professor himself explained why he was teaching difficult questions.

His reasoning was that if we practised challenging problems during preparation, the easier questions in the actual GATE exam would feel much more straightforward. Ideally, we would be able to solve them quickly and confidently.

I understand the logic behind that approach.

Preparing for difficult questions can improve conceptual understanding and make familiar problems easier to handle. There is value in being challenged rather than studying only the simplest examples.

However, I also have a concern.

Just because we need to complete the syllabus doesn't mean every lecture needs to become this long.

I'm watching recorded lectures, so I have the flexibility to pause, rewind, and take breaks. I genuinely feel bad for students who attended these lectures live. Sitting through such long explanations in real time, especially when the concepts become increasingly complicated, must be exhausting.

I am already feeling the pressure while watching the recordings at my own pace.

With GATE CSE 2027 preparation, there are several subjects to complete, revise, and practise. Time spent understanding one topic in extreme depth is time that cannot be spent on another topic.

I am not saying that difficult questions are useless or that the professor's approach is necessarily wrong. I can understand why he wants students to develop strong conceptual foundations.

My concern is about finding the right balance between depth and efficiency.

At some point, preparation has to move beyond watching lectures. We need time to revise what we have learned, solve GATE PYQs, identify mistakes, and understand how questions are actually asked in the exam.

If I spend all my available time watching lectures, I might finish the syllabus without having enough time to practise using that knowledge.

That is something I need to avoid.

What I Need to Do Next

For now, I don't want to abandon the lectures or assume that the difficult concepts are unnecessary.

Instead, I need to complete the first pass of the syllabus while keeping track of the areas that require more attention.

The relationships between SLR and CLR are one such area. I haven't understood them comfortably yet, so I will need to revisit them during revision.

I also need to remember that learning a topic for the first time and revising it later are different experiences. When I return to these concepts after covering more of the subject, some of the connections may become easier to understand.

At least, that is what I am hoping for.

The immediate priority is still to complete the remaining syllabus by October 31. After that, I want to spend more time on revision and question practice rather than continuing to consume lectures without enough opportunities to test myself.

Monday's Plan: One Lecture Is Enough

For Monday, I have decided to complete only Compiler Design Lecture 10.

The lecture is approximately 3.5 hours long, and the professor has said that it will explore more relationships between SLR and CLR.

I don't want to overload the day by adding more lectures on top of that.

Three lectures of 2.5 hours each were already hectic on Sunday. Adding another lengthy lecture without allowing myself enough time to process the material would probably make things worse.

So, Monday's plan is straightforward: complete Lecture 10, pay attention to the relationships being discussed, and avoid expecting myself to master every difficult detail immediately.

I still have the October 31 deadline to consider, so I cannot spend unlimited time on one topic. But I also don't want to rush through everything so quickly that I remember almost nothing later.

Finding that balance is becoming an important part of my GATE preparation strategy.

Day 42: Progress, Frustration, and a Reality Check

Sunday was not a bad study day. I completed three lengthy Compiler Design lectures and cleared the pending notes for two earlier lectures.

At the same time, I realised that the parsing concepts are becoming difficult to process when several methods and their relationships are introduced together.

I also found myself questioning whether such long lectures are the most efficient way to prepare when the syllabus deadline is close.

I don't have a perfect solution yet. For now, I will continue with the planned lectures, keep track of my weak areas, and make revision and question practice a priority once the first pass is complete.

Tomorrow, it is just one lecture: 3.5 hours of SLR, CLR, and whatever additional relationships await me.

Day 42 complete. Three lectures finished, pending notes cleared, and my patience with lengthy lectures officially under review.