c/coding-for-beginners

Spent 4 hours debugging a missing semicolon in Python... which doesn't even need semicolons

I was following this tutorial on YouTube and copied some JavaScript code by accident. Spent forever checking brackets and indentations. Finally asked my friend to look at it and he just laughed. Felt like an absolute fool. Has anyone else wasted time on something that dumb?

I finally found a way to debug Python without losing my mind

I kept getting these weird errors in my code and spending hours staring at it. Then I started using print statements with specific markers like 'step 1 done' and 'step 2 done' to see where it breaks. It sounds dumb but it helped me find a bug in a loop that was running 500 times in under 10 minutes. Has anyone else tried this or is there a better way for beginners?

Tutorials that copy paste from documentation are useless for beginners

I noticed this pattern after trying to learn Python for about 2 months. Every tutorial I found on YouTube just copies the code from the official docs and reads it out loud. But they never explain WHY you'd use a for loop over a while loop in a real situation. My buddy who codes for a living told me "the docs tell you what, not when" and that clicked for me. Has anyone else found a resource that actually teaches the thinking behind the code?

Started using git for my grocery list and it actually works

Switched from IDEs to plain text editors 6 months ago and wish I'd done it sooner

I used to rely entirely on VS Code with a million extensions for small python scripts. Then I took a Linux class at my local community college that forced us to use nano for everything. After 3 weeks of pure frustration, I realized I actually learned the code better without all the autocomplete crutches. Has anyone else tried ditching their heavy IDE for something like Sublime or even just vim?

The whole "just Google it" advice is driving me nuts

I keep seeing people tell new coders to just Google their errors, but that's terrible advice for someone who doesn't even know what keywords to search for. Last week I spent 3 hours on Stack Overflow because I kept typing "array not working" instead of "undefined index offset" - two totally different things. If you're helping a beginner, at least give them the right terms to look up first. Has anyone else noticed this causing more frustration than it solves?

Used to hate code comments until a senior dev showed me a messy function from 3 years ago

I always thought comments were a waste of time because the code should speak for itself. Then last month a senior dev at work pulled up a function I wrote 3 years ago that had zero comments and was a complete mess. I couldn't even figure out what it did without spending 20 minutes tracing variables. He showed me the same function after he added 5 comments, and it suddenly made sense in under 2 minutes. Has anyone else had that moment where something you ignored suddenly clicked?

Hot take: that full week I spent debugging ONE missing semicolon taught me more than any tutorial ever did

I remember that Thursday afternoon in May when I was building a simple calculator app for my first portfolio project. I spent 7 straight days staring at the same error message in VS Code, convinced the framework was broken. Finally on Sunday night at 2am I noticed a missing ; in a code line I had rewritten 12 times. Everyone online says to use linters and IDE tools to catch these instantly. But honestly that frustration forced me to actually READ error logs line by line, google each part, and understand how the code connects. Without that painful week I would have just copied and pasted solutions. Does anyone else think the struggle is actually more valuable than the shortcuts?

Stumbled into a code review at a local meetup back in 2019 that changed how I write comments

I was at this small meetup in Austin and someone pulled up my pull request on the big screen. They pointed out I was explaining WHAT the code did instead of WHY it was done that way. Has anyone else had a similar moment where a small habit got completely flipped?

PSA: A library user in Seattle showed me why I should lint my Python code

I was helping a guy debug a script at the downtown Seattle public library last month, and he pointed out how messy my indentation was. He showed me how a linter catches spacing issues and missing colons before you even run the code. I spent maybe 30 minutes setting up flake8 in VS Code after that chat. Has anyone else had a random stranger at a coffee shop or library teach them a coding habit that stuck?

TIL a single missing semicolon cost me 4 hours of debugging

I was working on a simple JavaScript function last night to sort an array of numbers. The code looked fine to me, no red underlines in VS Code, no errors in the console at first glance. But the output kept coming back in the wrong order no matter what I tried. After about 2 hours I started checking line by line, even rewrote the whole function from scratch. Turns out I forgot a semicolon after a variable declaration way up top, which broke the next line's logic in a weird way. It took another 2 hours before I finally noticed it while squinting at my screen at 1 AM. Has anyone else wasted a whole evening on something as tiny as a missing character?

Tried to code a calculator in Python and it kept telling me 2+2 = 22

I'm like 3 weeks into learning Python, just doing basic stuff. So I figured I'd write a simple calculator that adds two numbers. Simple, right? I wrote the whole thing, ran it, and typed in 2 and 2. It printed out 22 instead of 4. I stared at my screen for like 10 minutes thinking I broke math itself. Turns out I forgot to convert my input from a string to an integer. The program was just gluing the text together instead of adding numbers. My buddy who's been coding for years saw me screenshot my code and send it to him in a panic. He just laughed and said "classic rookie move." Has anyone else had a moment where you spent way too long debugging something that was just one tiny thing? I feel like I need to write a checklist for myself or something.

Just realized I was commenting code like an idiot for 6 months

I used to write stuff like 'this adds the numbers' right next to a line that literally says 'x + y'. Thought I was being thorough. Then a senior dev in my online bootcamp straight up told me my comments were useless and actually made the code harder to read. He showed me a fix where I explained the why, not the what, like 'handles edge case when user enters zero'. That one tip saved me so much time debugging last week. Has anyone else had their code comments ripped apart and learned something from it?

Tried learning Python through a YouTube course and ended up more confused than when I started

I got about 3 hours into a 12 hour Python series and realized the guy was using outdated syntax from 2015. Has anyone else hit a wall with a tutorial that just didn't click for them?

Question about my first Python project falling apart at line 47

Spent 6 hours building a simple calculator for my class project and the whole thing crashed when I tried to add decimals. My if statements kept skipping the float conversion and I had no clue why until a buddy pointed out my indentation was off. This is the third time tabs have messed me up and I'm starting to think I need a different editor. Does anyone else deal with these tiny syntax errors that eat up your entire afternoon?

Why does nobody talk about learning Python vs JavaScript first?

A buddy in my coding group swore I should start with Python. Said it's easier for beginners. I ignored him. Went straight to JavaScript. Three months in and I'm stuck on DOM stuff. He's building simple scripts already. Was he right? Or is JavaScript better in the long run? Which side do you pick?

Spent 40 minutes debugging a missing semicolon and now I triple check every line

I read on a dev blog yesterday that beginners waste an average of 30-60 minutes per session on tiny syntax errors like that, and it made me realize I need to slow down instead of rushing through code, anyone else still falling for these basic mistakes after months of practice?

Learned the hard way why you shouldn't name your variables 'data'

I was working on a little Python project for my portfolio, and every single function I wrote had a variable called 'data'. List of user info? data. Dictionary of scores? data. String from an API call? you guessed it, data. Then I tried to debug a loop after 3 days away from the code and I couldn't tell what anything was doing. I spent 2 hours just tracing which 'data' was which. That's when it clicked for me. Now I name things like 'user_scores' or 'api_response' and my code makes sense the next morning. Does anyone else have a bad naming habit they had to break?

Stumbled into building my first working calculator script in Python today

I was just messing around with a tutorial online and decided to add my own twist by making the calculator handle division by zero. To my surprise, it actually worked after fixing a typo where I forgot a colon. I typed 10/0 and it returned 'Error: cannot divide by zero' instead of crashing. Took me about 45 minutes to get it right with the if-else logic. Has anyone else hit a small win like this that felt way bigger than it should have?

Just realized I was writing Python functions wrong for months

Started learning Python back in February to help automate some route planning stuff for work. Been watching tutorials and following along, writing functions that take like 6 or 7 parameters. Last week I tried to reuse one of my older scripts for a new route and spent 3 hours debugging because I forgot which parameter went where. A guy on Reddit pointed out I should use default arguments or *args and **kwargs. Fixed it in 10 minutes. Has anyone else had that moment where you realize you've been making things 10x harder than they need to be?

Picked Python over JavaScript for my first language. No regrets 6 months later.

I started learning to code back in March. Couldn't decide between Python and JavaScript. Everyone said JS was more useful for jobs. But Python's syntax just clicked with me faster. After 6 months I can build small scripts that automate my spreadsheet work. Got a little dashboard going that pulls data from 3 different sources. It's not pretty but it works. Has anyone else gone against the popular advice and stuck with their gut?

Finally figured out why my code kept breaking - turns out it was semicolons

I used to just copy code from tutorials and hope it worked. But last week I was stuck for 3 hours on a simple loop because I kept missing semicolons in JavaScript. My friend pointed out that I was writing 'let x = 5' without the semicolon at the end, and once I added them all, everything ran. Has anyone else had a tiny syntax thing take forever to figure out?

Why does nobody talk about how bad most coding tutorials are for beginners?

I tried learning Python last month and every tutorial jumps straight into loops and functions before explaining what a variable actually does. It took me 3 hours on YouTube just to find one guy who broke it down like I was 5. Why is this so hard to find?

Appreciation post: I thought learning to code would be way too hard for me

Honestly, for a long time I was sure I just wasn't a 'computer person' and could never learn. Then my friend in Chicago said I should just try a free hour on Codecademy, no pressure. I did their first Python lesson about printing messages, and it actually made sense. After doing that for 30 minutes, I realized it's just about following clear steps, not some magic. Has anyone else had a moment like that where something just clicked?

I finally bought a $150 online course on Python that turned out to be a total waste.

The lessons were just a guy reading slides and the code examples were full of errors. I spent a month trying to make sense of it before giving up and using free tutorials instead. Should beginners ever pay for courses, or is everything we need really free online?