How I Learned to Stop Worrying and Love NSU!

Objectives

  • Share with newcomers the tale of the eventful adventurous journeys of a few NSU ECE students. .

  • In a rapidly evolving world of computer science and engineering, it is essential to stay current with emerging concepts while mastering the fundamental knowledge of systems and theory. Stories stated anonymously are all from our students who voluntarily came forward to share their respective experiences and views that help them survive, sustain, and capitalize meaningfully in their academic journey at NSU. These are individual experiences shared voluntarily by a few of our NSU students, and DO NOT represent anything obligatory in any aspect.

Anonymous Participant 1

  • The first two semesters are usually the scariest for everyone since NSU is an unknown territory for newcomers. At first, it was hard for me to decide how much I needed to study to secure an A,A-. Eventually, I realized that you need to study smart rather than just studying a lot.

  • For example, in math, it's better to practice variations of problems instead of repeating the same type again and again. Try to visualize the problem geometrically and understand how it's solved, not just what the final answer is. For CS, simulate the flow of a program on paper even if you could code it directly in an IDE. Focusing on the intrinsic logic sharpens your brain.

  • When I started my undergrad journey, there was no GPT. The sheer happiness of writing a thousand lines of code was incomparable. In CSE115, I used to collect mid/final problems from almost all faculties and solve the hardest ones just for fun. But after my first semester, I was introduced to competitive programming– and that humbled me. The problems I once thought were challenging turned out to be labeled as “very easy” in that world. I struggled with concepts like time complexity and dealing with time limit exceeded errors.

  • That's when I realized academia gives you the foundation, but building the entire structure requires extra effort. So, I shifted my focus toward problem solving, which later paid off a lot. For example, I was already proficient in DSA before taking CSE225, knew many algorithms before CSE373, and even had some knowledge of cache and optimizations before CSE332. I developed an intuitive understanding of recursion and even why stack overflow happens in memory. Still, I know there's always more to learn.

  • One lesson I've picked up over time: build projects. That's really, really important. The other day, someone showed me a chess engine they had built, and it was incredibly inspiring. (He's in his 3rd semester) Projects not only reinforce what you've learned but also teach you things no classroom ever will.

  • As time passes, people seem to be reading less and less, possibly because AI can now summarize almost anything. But I believe it's better to read than to get the direct answer from a summary. Using AI to get the answer right away will make your thought reach a tunnel vision. In CSE173, I read Kenneth Rosen's book thoroughly, in 373 I read more algorithms than what was taught in class. I also explored blogs and articles on various computer science topics. This habit of reading stuck with me and turned out to be invaluable. No matter what field you pursue, reading is essential. If you become a software developer, you'll need to read documentation constantly. If you pursue research, reading is the core of your work. Either way, strong reading habits will give you an edge.

  • Besides CS, I also really enjoyed the sociology and political science courses I took. In another life, I might have pursued one of those fields. If I could go back in time and restart my undergrad, I wouldn't change much, except I would begin my research journey earlier. Back then, I thought research was something you could only pursue in your final year. But looking back, I realize I could've started earlier, at least by exploring theoretical concepts. That would have prepared me much better for the deeper work that's needed in today's world.

  • Social media and peer pressure can be distracting. Personally, I avoided brainrot reels by consciously reducing my mobile usage and shifting most of my work and leisure to my PC, where it's easier to utilize time productively. I tried replacing some of that time with coding contests, blogs, or meaningful conversations. You'll be surprised how much it helps. For example, during an internship interview, I was once asked a question about secure transmission over the internet. I hadn't read that in a course, but just the day before, I'd been chatting with some people about how a chat platform could run inside an ISP connection without using the internet. That conversation gave me just enough background to answer the question.

  • That being said, maintaining having a social life is important. Balance is crucial, you can't let life become monotonous. Being aware of when to focus and when to take a break helps ensure a smoother and more meaningful academic journey. Read books, watch interesting movies. In the end, knowledge is everywhere, you just need to go out and grasp it.

Anonymous Participant 2

My initial encounter with the academic scene at NSU led me to develop a few study habits. If you are on the same boat as me - feeling disconnected from the material you are studying, or struggling to cope up with the pressure , here are some concrete steps you may take that can help you. These include simple rules I have set for myself and followed since my very first semester, and some that I have picked up along the way.

  • A weekly to-do list can keep you from feeling overwhelmed by tasks/homework/assignments. I create a Google Calendar at the beginning of every semester with my classes and holidays. Add exam/due dates to the calendar so that you don't miss any deadlines.

  • Courses which rely only on slideshows make me feel disengaged from the subject matter. (Is reading a summary of a novel and reading the book itself the same experience?) I read the preface/intro of the textbook chapter right before attending the lecture to get a gist of the topic, and the rest of the chapter after class to get a better understanding.

  • Compile your own question papers (QPs) and solve them (it may just be the end-of-chapter questions in a word doc). Time yourself. I carry these QPs in my bag at all times. Code taking long to run? Break between classes? Use the waiting time to solve your QP. The minutes add up to hours of practice. (Also helps you get accustomed to exam conditions, and can prevent exam anxiety.)

  • If you are just starting your undergrad as a CS student, programming should not feel like a boring task to you , and it should not be something you do only for the grade! Start with the simplest problems you can find online. Regular programming practice can build confidence and give you a sense of accomplishment! (I committed to 1-2 hrs of programming practice daily in my first two semesters.)

  • You should fully absorb the theoretical fundamentals that are taught in Programming Language - I and II. If you cut corners now, you may have a difficult time in future courses.

  • Lastly, we all start university with hopes of unlocking our full potential, but the academic stress can overwhelm us into taking shortcuts. We forget our initial purpose. If this happens, it is important to take a step back and rethink the greater motivation of your education.

Anonymous Participant 3

test