u/More-Station-6365

I used to think studying harder right before exams was the answer. Spoiler: it's not. Here's what actually helped me when I finally got my exam prep right.

The week before your exam, try this:

Day 7-6: Big Picture Review

Don't start with details. First go through all topics quickly and mark what you know and what you don't. This saves so much time later.

Day 5-4: Focus on Weak Areas Only

Forget what you already know. Put all energy into topics that are still unclear. This is where most students waste time by re-reading easy stuff.

Day 3: Past Papers Only

No more reading notes. Just solve previous year questions. This tells you exactly what kind of questions actually come in exams.

Day 2: Quick Revision

Go through only your weak points one more time. Keep it light — 2 to 3 hours max.

Day 1 Before Exam:

Rest Seriously. Sleep early. Eat properly. A fresh brain performs way better than an exhausted one that studied till 3am. The biggest mistake students make is studying randomly without a plan. Even a simple day-by-day structure makes a huge difference.

Struggling with my coding assignments and looking for a legit homework help site for programming. Most of the ones I've tried either feel like a scam or just send completed code with zero explanation.

I don't want someone to just do my programming homework for me I want to actually understand the logic and fix my debugging errors myself next time.

Looking for something like an online programming tutor or assignment help service that walks you through the problem step by step. Paid services are fine as long as they're worth it.

What has actually worked for you? And what should I avoid?

Hey r/learningprogramming, posting here because I want honest feedback from people who are actually learning or have recently learned programming. I've been teaching an introductory programming course at a US college for a few years now. And every single semester without fail I see the exact same pattern in the majority of my students. They follow my lectures perfectly. They answer questions correctly in class. They can read code and explain what it does. But the moment I give them a blank editor and say "now write this yourself" — they freeze completely. It doesn't matter how simple the task is. Even students who seemed confident during the lecture suddenly don't know where to begin when there's no example in front of them. The specific patterns I keep noticing are: Students understand a concept while watching but can't reproduce it 10 minutes later without reference material. They know the syntax but don't know how to break a problem down into steps before writing code. They treat every new problem like they've never coded before even when it uses concepts they've already learned. They get stuck on errors and immediately ask for help instead of trying to read and understand the error message first. I've tried different teaching approaches — more examples, fewer examples, more practice time, pair programming — but this gap between understanding and independent writing keeps showing up. My honest question to this community is — if you've been through this struggle yourself, what finally helped you bridge that gap? Was it something a teacher did differently, a practice method that worked, or just time and repetition? I'm genuinely trying to improve how I teach this and I feel like the people learning it have more insight than most teaching guides do.

Hey r/learnpython, posting here because I genuinely want some perspective from people who have learned Python recently. I teach an intro CS course at a community college in the US. Three years in and I keep seeing the exact same struggles in almost every student, regardless of how I try to explain things. The weaknesses I see most often are: Students can follow code line by line but completely freeze when asked to write something from scratch. Even simple stuff like "write a function that takes a list and returns only the even numbers" causes panic. They memorize syntax but don't understand why. They know how to write a for loop but have no idea what's actually happening underneath it. OOP is where almost everyone falls apart. Classes, self, init — I explain it the same way every semester and maybe 30 percent of students actually get it by the end. They don't debug, they just delete and rewrite. Reading an error message and actually using it to fix the problem is a skill almost no one comes in with. They rely too heavily on copying examples. The moment the problem looks slightly different from what they've seen, they're lost. Here's my honest question for this community — especially if you've recently learned Python or are still learning: Was there a specific moment or explanation that finally made things click for you? Is there something your professor said or did that actually worked? I'm genuinely trying to improve how I teach this and I feel like I'm missing something. Any honest answer helps, even if it's critical of how professors typically teach this stuff.

EE junior here. I was putting in more hours than ever and still failing every practice exam. Took me way too long to figure out what was wrong. I was confusing familiarity with understanding.

Reading solved circuit problems and nodding along feels productive. Your brain recognizes the steps and tells you "I got this." Then you sit down for the real exam with a blank circuit and your mind goes completely empty. That recognition feeling is not understanding.

What actually fixed it:

Covering the solution completely and solving from scratch every single time. Painful and slow at first. But if I couldn't do it with the solution covered, I didn't actually know it.

Also started doing old exams three weeks out instead of three days before. Three days out you're just measuring how panicked you are. Three weeks out you still have time to fix what's broken. Finished with a B. Not perfect but I actually understood the material this time.

Every time I get stuck on an assignment, I go looking for help online and end up in the same frustrating loop either I find a forum post with a one-line answer and no explanation, or a site that just rewrites my code without telling me what I was missing. I don't want the answer handed to me. I want to understand why my logic broke down in the first place so I don't hit the same wall next week. Ideally looking for something where I can share my code or describe what I'm trying to do, and get a step-by-step breakdown of the reasoning not a corrected version that I just copy and move on from. If it also has targeted practice for weak spots, even better. Not looking for a ranked list of platforms looking for what actually clicked for someone who was at that early stage where you don't even know the right questions to ask yet. Free or paid doesn't matter, quality does.

Civil Engineering junior here. Statics was the class that almost made me switch majors. Failed it twice and spent a long time trying to figure out what was actually going wrong.

Third attempt i passed with a B+. Here's what actually changed. The problem wasn't effort it was how i was studying.

I was re-reading textbook examples and thinking I understood them. But re-reading someone else's solved problem is completely different from solving one yourself from scratch. My brain was recognizing the solution, not actually understanding it. What finally worked:

1. Drawing free body diagrams for everything even simple problems

I was skipping this step to save time. Turns out that step IS the thinking. Once i forced myself to draw every single FBD before touching an equation, my error rate dropped significantly.

2. Solving old exam problems without looking at solutions first

Uncomfortable and slow at first. But this is literally what exam conditions feel like. I started doing this three weeks before the final instead of the night before.

3. Finding where my understanding actually broke down

Instead of moving on when something felt confusing, i stopped and figured out exactly which concept I didn't understand. Most of the time it traced back to one small foundational gap.

4. Sleep before exams not one more hour of studying

The exam i passed with the highest score was the one I slept 8 hours before. Sounds obvious but engineering students rarely actually do this.

Two failed attempts taught me more about how to study than my entire high school career did.

Hey r/learnpython, genuinely need some help here. I'm a sophomore CS student in the US and I've been using Python for about a year now. Variables, loops, functions all fine. But the moment my professor introduced Object Oriented Programming, I completely lost the plot. Like I get the definition.

A class is a blueprint, an object is an instance. I can repeat that back all day. But when I actually sit down to write a class from scratch for a real problem, I have no idea when to use a class vs just writing a regular function.

For example my professor gave us an assignment to model a simple bank account using OOP. I understood what a bank account does but I had no idea how to think about it as a class.

I ended up just copying the structure from the lecture slides without really understanding why it was built that way.

My specific confusions are:

When should I actually use a class vs just a function? What goes inside init and why? What does self actually mean and why is it always there? How do I know what should be an attribute vs a method?

I've re-read my textbook and watched my professor's recorded lectures twice but it's still not clicking. Is there a different way of thinking about OOP that helped it finally make sense for you?

Any help appreciated even if it means I need to go back to basics.

I've been working with Excel for years and genuinely enjoy helping people get unstuck. Whether you're a complete beginner or just running into a specific issue, feel free to drop your question below.

I can help with things like:

• Understanding how formulas work (VLOOKUP, IF, SUMIF, INDEX/MATCH, etc.)
• Formatting cells, rows, and sheets for better readability
• Organizing and cleaning up messy data
• Using filters, sorting, and basic charts
• Automating repetitive tasks with simple macros
• General "why isn't this working?" questions

How to get the best answer from me:

Describe what you're trying to do, what you've tried so far, and what's going wrong. Screenshots or sample data (even pasted as text) are a huge help. The more context you give, the faster I can point you in the right direction.

No question is too basic — if Excel is giving you trouble, just ask. Happy to help.

Hey everyone, looking for some honest advice here.

I'm a final year computer science student in the US and I've used Python throughout college — assignments, a few projects, one data structures course. But here's my problem: I can follow along with code just fine, but the moment I close the tutorial and try to build something on my own, I completely blank out.

Like I'll understand the concept while watching or reading, but then I sit down to actually write it from scratch and I don't even know where to begin. It's honestly frustrating because graduation is a few months away and Python keeps showing up in job descriptions I'm interested in.

Specifically I struggle with:

• Starting a project without a template or guide to follow
• Knowing when to use functions vs classes
• Working with real data using pandas without copy-pasting examples
• Writing code that's clean and not just "works but looks like a mess"

I've tried doing small exercises but I feel like I'm just going through motions without building real confidence.

Has anyone been in this exact situation before? What actually helped you go from "I can read Python" to "I can actually build things in Python"? I have around 4-5 months before graduation so I want to use that time properly.

Appreciate any advice — even if it's tough love.

Junior year ME student here. For two years straight i lived on caffeine and 3am study sessions before every major exam. My grades were average at best and i was constantly burned out.

This semester i forced myself to completely change the approach and the difference has been significant enough to share.

The biggest shift — spacing everything out over 7 days minimum.

Instead of cramming the night before, i now hit the same material on day one, day three, and day seven after first learning it. Sounds simple but most engineering students never actually do this because problem sets and lab reports keep pushing it off.

Second — solving problems without looking at notes first.

Engineering exams don't give you your notes. So why study with them open the whole time? I started closing everything and attempting problems cold. Uncomfortable and humbling but that's exactly where retention happens.

Third — environment consistency.

Same chair, same desk, same time. Took about two weeks but my brain now shifts into focus mode much faster just from the routine trigger alone.

Fourth — 8 hours of sleep before any major exam, no exceptions.

The exam I performed best on this semester was the one I slept a full 8 hours before. Not a coincidence after seeing it happen repeatedly. None of this is complicated but it took genuinely bad grades to make me actually commit to it.

four years in and looking back there were a few things that genuinely made the difference between passing and actually understanding the material.

the first was forming a study group with people who were slightly better than me. not to copy their work but to watch how they approached problems.

engineers who are good at problem solving think differently and being around that changes how you start to think too.

the second was drawing everything. circuits, force diagrams, system diagrams, whatever it was. if i could not draw what was happening i did not actually understand it.

the drawing forced me to slow down and identify exactly where my understanding broke. the third was going to office hours not when i was stuck but before i got stuck. showing up with questions about the upcoming material instead of the assignment i was already behind on changed my relationship with professors completely.

they noticed and it mattered at the end of the semester. the last one was accepting that confusion is part of the process and not a sign that you are in the wrong major. every engineer i know who is now working felt completely lost at some point during school.

the ones who stayed were not smarter. they just did not let the confusion convince them to quit. what helped you get through the harder semesters

four years of CS and i can do a little bit of everything but i am not sure i am actually good at any one thing. everyone around me seems to have figured out their path. frontend, backend, data, security. they all sound confident about where they are headed. i just feel like i have been taking whatever classes were required and now suddenly i am supposed to know what i want to do for the next few years. did anyone else feel completely undecided this close to graduation or does it actually sort itself out once you start applying

every time i think i finally understand how python works it hits me with an indentation error and i have no clue where the problem actually is. like i can see the code looks the same to me but python apparently disagrees. is there a simple way to actually understand what python wants here or is this just something you figure out by making the same mistake a hundred times

hey guys struggling with python lists for my assignment and i keep messing it up i understand the basic concept but every time i try to remove a specific item or update something at a certain index my code either throws an error or gives me wrong output

specifically confused about:

removing an item by value vs removing by index

what happens when you access an index that doesnt exist.

how to loop through a list and change items without skipping elements

feels like i understand lists until i actually have to use them in a real problem lol anyone who can break this down simply would really appreciate it