My Second Semester Story


🔄 Five Months of Silence, Five Months of Growth: My Second Semester Story

Hello everyone! Welcome back to Mayur's Tech Journey. 🚀

It has been exactly five months since I last wrote here. My last post went live on December 28, 2025 — and today is May 29, 2026. If you have been following this blog, you might have noticed the silence. No posts in January. No posts in February, March, or April. Nothing in May until now.

But I want to tell you something important: the silence was not emptiness. The silence was work.

Every time I thought about writing a new post, something was happening — a deadline, a project, an exam, a new friendship, a new line of code. I kept telling myself, "I will write soon." And now, finally, sitting here five months later, I realize I have so much to tell you.

So pull up a chair. This one is going to be a long read. ☕

📖 Where Did We Leave Off?

When I last wrote, I had just built my first JavaScript Calculator — a small project, but a massive personal milestone. I had spoken about how JavaScript felt like a foreign language at first, how eval() both scared and excited me, and how seeing my own code run on a browser screen for the first time felt like magic.

Before that, in "Fueling the Code," I had shared my Silver Stone badge on CodeChef, my HackerRank stars across C, C++, and Python, and the memory of 12:07 AM on June 16th — that quiet, trembling moment when my MHT-CET result lit up as 99.079 percentile and my father's stunned expression became the image I carry in my heart every single day.

And in "The Boy Behind the Percentile," I had been honest about the truth behind the scores — that I was never the "bright" student. That I was average, forged by effort, and still carrying the bittersweet weight of having earned a Tier-1 seat but sitting in a Tier-3 college due to financial constraints.

I left off by saying: "The fighter is alive."

Today, I'm here to prove it.

🏆 The Number That Changed Everything: 9.6 SGPA in Semester 1

Let me start with the biggest news first.

I scored a 9.6 SGPA in my very first engineering semester.

I am going to let that sit for a moment, because when I saw that result, I did not jump or shout. I just sat quietly, and the thought that came to me was — "The gate is still a reminder, but now the gate is also a proof."

For those who have been following this blog since the beginning, you know what that gate means to me. Every morning I enter Sanjivani College of Engineering, I am reminded of the dream I had to defer and the responsibilities I chose to carry instead. That 9.6 was not just a grade. It was an answer. To every doubt. To every person who questioned whether I had made the right choice. To myself on those late nights when I wondered if the struggle was worth it.

It was worth it.

Academics vs. Coding: The Big Myth

Now, if you are a first-year engineering student reading this and wondering whether academics and coding can truly go together — whether building projects and studying for exams are two things that fight each other — I want to be very direct: they do not fight. They feed each other.

The logical thinking you develop while debugging code makes theoretical concepts clearer. The discipline you build on platforms like CodeChef carries into your study schedule. I am living proof of this.

The formula is simple: Consistency + Curiosity = Results. It worked in 12th standard, and it worked in Semester 1 of engineering.

⚡ Semester 2 and the Exam That Is Coming

As of today — May 29, 2026 — my Second Semester End Semester Examinations begin on June 5th.

That is exactly 7 days from now.

I will be honest with you: the feeling is different this time. In Semester 1, I was still figuring out how engineering academics worked — the exam pattern, the kind of answers professors expect, the difference between understanding something and being able to write it in an exam. I was learning the game while playing it.

In Semester 2, I know the game. And I have played a much more active role — both inside the classroom and outside of it.

This semester has been heavier on the project side. There were moments when I genuinely wondered whether I was spreading myself too thin. Building projects, attending labs, studying theory, maintaining GitHub — it sounds glamorous on paper, but there are days when you are running on four hours of sleep and three deadlines.

But here is what I have learned: pressure reveals character. And I want to walk into that exam hall on June 5th as someone who did not just survive Semester 2 — but someone who built during Semester 2.

My revision is on. My formula books are out. The fighter, as always, is alive.

👨‍💻 The Python Chapter: When I Truly Felt the Power of a Language

If Semester 1 was my JavaScript and web development chapter, then Semester 2 has been — without any doubt — my Python chapter.

And let me tell you, Python changed something inside me as a programmer.

I had used Python before, loosely. I had earned 2 stars on HackerRank for Python, written some basic scripts, and moved on. But this semester, I did not just use Python. I lived inside it. I built with it. I failed with it. I debugged it at midnight. And slowly, I started to understand what all those experienced developers mean when they say Python is powerful.

Let me explain what I mean through the projects I built.

🛠️ The Projects: Where Theory Met Reality

Project 1 — SAFARNAMA: A Complete Travel Planning App

This was one of the most ambitious things I have attempted so far. Along with my teammate Rohit J. Khokale, I built SAFARNAMA — a full travel planning web application built entirely in Python using Streamlit.

SAFARNAMA allows a user to:

  • Enter their starting city and destination (across Hills, Coastal, and Devotional categories).

  • Calculate the real-world distance between the two cities using Geopy and geodesic coordinates.

  • Choose hotels from Luxury, Mid-range, and Budget tiers.

  • Plan their meals day by day from a structured hotel menu.

  • Track all expenses across transport, accommodation, food, activities, and miscellaneous costs.

  • Download a fully formatted PDF itinerary using the FPDF library.

Now, on paper that sounds like a feature list. But let me tell you what it actually felt like to build this.

The moment that hit me the hardest was the first time I ran the app and saw my Python function — a function I had written in the backend — instantly appear as a sidebar input widget on the screen. There was no HTML file. No CSS file. No JavaScript connecting the two. Just Python, talking to itself, and producing a working UI.

That was the moment I truly understood what people mean when they say Streamlit bridges the frontend and backend. Before SAFARNAMA, those two words felt like two different worlds with a wall between them. Streamlit taught me that in Python, the wall does not have to exist.

I also learned something important about file architecture during this project. Our destination data, hotel menus, and pricing information were all stored in a structured travel_data.json file. This sounds like a small decision, but it made an enormous difference. When we needed to add a new destination or change a hotel price, we just updated the JSON file — we did not touch the logic. That is what clean architecture actually means.

Travel Planner Interface


Project 2 — ScholarDesk: A Full-Stack Academic Web App

This one is close to my heart, because it is literally built for students like me.

ScholarDesk is a complete academic productivity web application built with Python and Flask, co-developed with my teammate Arjun B. Kadam. It is hosted live, and yes, you can visit it right now!

ScholarDesk is a unified workspace where any student can:

  • Create and manage their lecture notes in a personal cloud notebook.

  • Track tasks, deadlines, and exam milestones through a dedicated task scheduler.

  • Calculate their SGPA dynamically using course credits and grade points.

  • Monitor their attendance to make sure they stay above the minimum threshold.

  • Use a Pomodoro Timer for structured study sessions.

  • Log and audit their expenses through a personal finance ledger.

  • Chat with Saathi, an AI-powered study assistant built with Google's Gemini API.

ScholarDesk was my deepest dive into full-stack Python development. Unlike SAFARNAMA where Streamlit handled the UI, ScholarDesk needed Flask routing, session management, SQLite database design, and a modular feature architecture.

The session security system was something I spent considerable time on. Making sure that a user cannot use the browser's back button to return to a secured page after logout — that is not a feature you learn from a beginner tutorial. That is something you discover when you actually think about how real-world applications need to behave.

And Saathi — the AI chatbot — was my first hands-on experience integrating a live AI API into a working application. Connecting Google Gemini to a Flask route, handling the response, and rendering it smoothly in the UI was a genuinely fresh kind of excitement.

What These Projects Taught Me (Beyond the Code)

Building SAFARNAMA and ScholarDesk in the same semester taught me something that I want every engineering student reading this to hear clearly:

You do not learn to code by reading about code. You learn to code by building something that can fail.

When SAFARNAMA threw a GeopyError because a city name was spelled slightly differently, I had to handle that exception. When ScholarDesk crashed because of a session conflict on the login route, I had to trace the flow, understand the HTTP lifecycle, and fix it. These errors were not obstacles. They were the actual education.

Python gave me the vehicle. The projects gave me the road. And the road, as always, teaches you more than the garage ever will.






👥 The Friend Circle That Made It All Better

Now let me step away from the code for a moment — because this semester was not just about projects and percentages. I want to talk about the people.

When I first walked through the gate of Sanjivani College of Engineering, I carried with me the weight of a deferred dream. I knew nobody. I was the kid from the village with a 99 percentile who was trying to figure out where he belonged in a new city, a new campus, a new world.

Five months later, I can tell you: I found my people.

I have built a friend circle this semester that I genuinely did not expect to find. People who stay back after class to discuss a project idea. People who message you at 11 PM with a "bhai yeh error kyun aa raha hai?" and you spend the next hour solving it together — not because you have to, but because you want to. People who celebrate your 9.6 SGPA louder than you celebrate it yourself.

Arjun B. Kadam (my teammate on ScholarDesk) and Rohit J. Khokale (my teammate on SAFARNAMA) — these are not just collaborators. These are the kind of people who make you better by simply being around. The kind who push you, challenge you, and also remind you to eat dinner when you forget.

There is something I did not fully appreciate in those lonely 12th standard "ghost mode" preparation months: learning alongside people accelerates growth in ways that solo grinding simply cannot.

I came to Sanjivani expecting to study. I did not expect to build a team. But I did, and I am grateful for every single person in it.

🔁 Reflecting on the Five Months: An Honest Account

Let me be real with you, as I always try to be on this blog. These five months were not all wins and highlights.

There were weeks where I questioned everything. Weeks where I wondered if building projects was taking too much time away from academics. Weeks where I opened my laptop at 10 PM after a long day, stared at the screen, and did not write a single line. Weeks where the "ghost mode" focus that had served me so well in 12th standard felt impossible to find again — because college life, friends, deadlines, and lab submissions are very different from the disciplined isolation of competitive exam preparation.

I struggled with balance. I am still learning it.

But here is what kept me going: The memory of 12:07 AM never left me.

Every time I felt like stopping, I thought of my father's face in that dark room. The way he looked when the screen lit up and I whispered "Ninety-nine." That image is not motivation that fades after a day. It is fuel that does not run out.

And now I have a new image in my heart: the ScholarDesk app loading in a browser. Saathi answering a student's question. The SAFARNAMA PDF itinerary downloading. My own creations, working in the world.

Code is not just a skill anymore. It is becoming an identity.

🚪 Standing at the Gate Again: What Comes Next

Semester 2 exams start on June 5th. I am going in prepared.

After the exams, there is more to build. More to learn. More to document here on this blog — which I promise I will not abandon for five months again.

I am thinking about deepening my knowledge of Flask and backend architecture. I want to explore databases more seriously — not just SQLite, but understanding how data actually scales. I want to improve my DSA practice and get more disciplined on competitive programming platforms.

For my readers — whether you are a fellow engineering student, a parent watching your child navigate this journey, or someone who stumbled upon this blog from a search engine — I want you to know this:

Engineering is not a four-year course. It is a continuous, sometimes painful, always rewarding process of becoming.

And every time you feel lost, behind, or like you are the only one who doesn't have it figured out — remember that the person who once barely knew what a for loop was is now building AI-integrated web applications and scoring a 9.6 in the process.

The fighter is not just alive. The fighter is evolving. 💪

🔗 Also Read:

"Five months of silence. But not one moment of standing still."

Signing off,

Mayur B. Gund

FY  B.Tech CSE | Sanjivani College of Engineering

  





Comments

Post a Comment