c/coding-for-beginners

Tutorial videos or docs first? I flipped my opinion after 40 hours with both

I started learning Python about 3 months ago at the library downtown. First 2 weeks I watched every YouTube tutorial I could find, took notes, followed along. Felt productive but when I sat down to build a tiny calculator I froze. Then I switched to just reading the official docs and a simple book, no video. Slower at first but I actually remembered the syntax and could look things up faster. Now I think videos are good for ideas but docs are where the real learning lives. But my buddy swears the opposite, he needs someone talking him through it or he zones out. Which one worked for you when you were starting out? Or did you mix them somehow?

Lost 4 hours to a tool that checks if your code is formatted, no joke

Downloaded some linter plugin on a whim Tuesday night for my first real project. Spent 4 hours fighting with config files and reading GitHub issues. Turns out I forgot to install the actual linter program, just the editor addon. 0 dollars lost but my whole evening gone. Has anyone else sunk time into a tool setup that ended up being a one line fix?

Spent 4 hours debugging a missing semicolon in JavaScript

Last Tuesday I was working through a beginner tutorial and my whole script just stopped running. No errors in the console, nothing. I checked my brackets, my variables, even restarted the browser twice. Turns out I forgot a semicolon on the line right after a loop, and the interpreter just silently skipped everything after it. Four hours. Four hours for one tiny character. My roommate suggested I try a linter, and now I run one before I even open the console. Has anyone else had a bug that took way longer than it should have because the error message was basically nonexistent?

Serious question, how long should a beginner's 'quick bug' actually take?

Spent 3 days tracking down a missing semicolon in a JavaScript loop last month, and I genuinely cried at my desk in Austin. Is that normal for a newbie, or should I be worried my problem-solving is slower than it should be? How long did your dumbest bug eat up?

Bought a $60 Udemy course, ended up learning more from free YouTube

I grabbed a Python course on sale last month because I kept getting stuck on loops and dictionaries. The videos were fine but the instructor went way too fast and the practice problems felt impossible. Has anyone else had better luck just following free tutorials and building small projects instead?

Spent 2 years overcomplicating CSS, a 12 year old set me straight

Wrote 500 lines of code before realizing I was using the wrong loop structure the whole time

I spent 2 days debugging JavaScript for a landing page and it turned out forEach was way cleaner than the nested for loops I kept forcing. How did you figure out you were overcomplicating things?

Showerthought: That "perfect" code tutorial set me back more than it helped

I spent 3 months last year following a popular Python course on Udemy. The guy teaching it was this super clean, polished YouTuber type who made everything look easy. But when I sat down to build my own project, a simple to-do app for keeping track of my garden plantings, I froze for 2 days. I realized he never once showed us what to do when you hit a bug or when the code just breaks in real life. I finally asked a buddy who's been coding for 10 years, and he told me to just Google the error and start fixing things. That was way more useful than the whole course. Am I the only one who feels those perfect tutorials are a trap for beginners?

Unpopular take: I think starting with Python is actually a bad idea for most beginners

I know everyone says Python is the way to go for new coders, but after teaching 3 friends who all quit within 2 months, I changed my mind. The problem is Python hides too much stuff - like indentation being syntax, dynamic typing, and all those magic methods. My buddy Dave spent 3 weeks debugging a bug that was just a tab vs spaces issue. I've seen way better results when beginners start with something like JavaScript or even a bit of C, because you actually see what the computer is doing. Python makes you feel like you're coding until you hit a wall you can't explain. Has anyone else seen new coders bounce off Python harder than expected?

TIL resetting my CSS fixed a layout I'd been fighting for 3 days

I was building a simple portfolio page for like a week straight. Every time I added a new section, the whole thing would just break. Finally my buddy Mike came over and was like "did you set a box-sizing border-box?" I had no idea that was a thing. Turns out my padding was making everything spill out of the container. Has anyone else spent way too long on something this basic?

That time a senior dev laughed at my for-loop question in a Slack channel

I asked how to optimize a nested loop in the company coding chat, and a guy with 15 years experience just replied 'lol.' Has anyone else dealt with senior devs who treat questions like they're stupid?

Got told my code was 'too clever' by a senior dev

They said I was writing one-liners that no one else could read, so I started breaking it into stupid simple steps. Anyone else get called out for showing off instead of being clear?

Dropped $200 on a bootcamp and it was a total waste

I signed up for this 8 week web dev bootcamp thinking it would fast track me into a job. It was just them reading slides and giving basic homework. Learned more in a free YouTube series in like 3 days. Anyone else get burned on a paid course like that?

Did my first project in Python after 6 months of JavaScript - huge difference in readability

I spent the last half year learning JavaScript for web stuff and finally gave Python a try last week for a data sorting script. Python took me like 3 lines to do what took 15 in JS, and I didn't even need to use curly braces or semicolons. My code looked cleaner in like 30 minutes than my JS projects ever did after 5 hours of debugging. Anyone else switch languages and notice a massive shift in how easy it is to follow your own code?

I finally saw how bad my code comments were after helping a friend

My buddy asked me to look at his beginner Python script last weekend at a coffee shop near downtown. I opened his file and everything was clear because he wrote short notes about what each function did. Then I looked at my old projects and realized I had zero comments or just stuff like 'this works' which is useless. Now I am going back through my code and adding real explanations for future me.

Spent 3 hours debugging a missing semicolon in JavaScript last night

I was working on a simple calculator app for my first real project. Everything looked fine to me but the code just wouldn't run. After staring at it for what felt like forever, I finally noticed I forgot a semicolon on line 47. My husband laughed when I told him, but honestly it made me realize how much one tiny character matters. I started using a linter plugin after that and it caught three other small errors right away. Anyone else have a moment where one small typo drove you crazy?

Hit 100 solved problems on Codecademy and it finally clicked

I've been messing with Python off and on for about 8 months, but last Wednesday I hit 100 exercises done on the platform. That number surprised me because I thought I was still stuck on the basics, but seeing the list of actual completed code made me realize I'd learned loops, functions, and even some file handling without really noticing. It was like a mental shift where I stopped feeling like a total impostor and started thinking I could maybe build something real. Has anyone else had a milestone number like that make the whole learning path feel different?

Shoutout to the guy who told me to just copy-paste code from Stack Overflow

My buddy Mark kept saying I should just grab code snippets from Stack Overflow instead of writing everything from scratch. I ignored him for 2 months, struggling through a Python script for work. Finally tried it last week and got my whole inventory tracker working in 3 hours instead of 3 days. Has anyone else felt guilty about copy-pasting code at first, then realized it's totally fine?

I changed how I name my files after one bad feedback session

Someone on here told me naming files 'final_v3' was just asking for trouble, and they were right. I switched to a date+project system and it saved me from sending the wrong version to a client last week. Has anyone else had a simple naming habit totally mess up their workflow?

Unpopular opinion: freeCodeCamp's projects aren't teaching real problem solving

I spent 3 months grinding through freeCodeCamp's curriculum and felt pretty good about myself. Then I tried to build a simple to-do list app on my own last Tuesday and completely froze for two hours. The guided projects hold your hand too much, you never have to figure out where to start by yourself. Has anyone else hit this wall where the tutorials make you feel ready but the real world proves otherwise?

Talked with my cousin about why I keep quitting coding and it hit different

Last weekend my cousin asked me why I keep starting coding courses but never finish them. She said it sounds like I treat each lesson like a test I have to pass instead of a tool I can use. That really hit me because she was right. I spent 3 months on a Python course and dropped out when I couldn't debug a script for a simple calculator. I was so focused on getting everything perfect the first time that I forgot coding is supposed to be messy. She told me about how she learned guitar by playing wrong notes for weeks until they sounded right. I never thought about learning to code like learning an instrument where mistakes are part of the process. Has anyone else had that moment where someone described your learning style and it completely changed how you look at coding?

That "just use console.log" advice almost cost me a whole day

I was reading a beginner thread on another forum where someone said "just use console.log" for everything. So I spent like 6 hours trying to debug a function that wasn't returning what I expected, just logging values here and there. Has anyone else tried using a proper debugger tool and found it way faster for tracking down the actual flow of your code?

Been teaching Python to beginners for 5 years and one mistake keeps showing up

Every single person I've helped seems to think they need to memorize every function before they write anything. I've seen maybe 30 beginners try to learn coding like it's a history exam with flashcards. Then they get stuck on week two because they can't recall the exact syntax for a for loop. You don't need to know it all by heart. You need to know how to look it up fast and apply it. I still Google basic stuff every day at my shop's computer system. Why are people so scared of using documentation?

Tried to add a simple search bar and broke my whole site for 3 hours

I was coding at my kitchen table last Tuesday, just trying to add a search bar to my practice blog. I copied some jQuery code from a tutorial, pasted it in, and suddenly my whole homepage went blank. Took me 2 hours to realize I forgot to close a script tag, then another hour to undo the mess. Has anyone else had a tiny typo wreck their whole project like that?

Just realized my code broke because of one missing semicolon

Spent Tuesday afternoon debugging a script for a school project. Turns out a missing semicolon on line 47 was making my whole loop crash. Half of me says linting tools catch this, but the other half thinks beginners need to learn to spot these manually. Which side do you lean on for building good habits?