c/coding-for-beginners

My sister said she 'couldn't see the code' when I showed her my project

I was showing my sister a simple Python script I wrote that prints a greeting. I had it all in one big block. She said, 'It just looks like a wall of text to me, I can't see where one part ends and another starts.' That hit different because I never thought about how code looks to someone brand new. I went back and added blank lines between the import, the function, and the main call. It took five minutes but made it way clearer. Has anyone else had a simple comment make you totally change how you format your beginner projects?

Just realized my entire Python script broke because I used a comma instead of a dot

I was trying to make a simple calculator in my room last night and it kept giving me a 'TypeError' for over an hour. Turns out I wrote 'print(total,2)' instead of 'print(total.2)' when trying to show two decimal places. Has anyone else lost a bunch of time on a tiny syntax mistake like that?

My first Python script took 3 days to write but now I can do it in 20 minutes

I spent last month building a basic script to sort my photos by date, and it was a total mess of googling and trial and error. After finishing a free online course that focused on functions and loops, I rewrote it from scratch in under half an hour. Do you think structured learning is better than just trying to build something right away?

Warning: I just learned how many lines of code are in a simple web page

I was reading an article on a dev blog yesterday about how browsers work. It said when you load a basic page, like a Google search, your browser is actually running millions of lines of code just to show it to you. I always thought a blank page with a search bar was maybe a few hundred lines, tops. That blew my mind. Does knowing how much complex stuff is happening behind a simple 'Hello World' page make you want to learn more, or does it just feel overwhelming?

Just figured out why my loops kept breaking and it's so simple

I've been learning Python for about two months now, and I kept running into this weird bug where my for loops would stop early or skip items. Turns out, I was changing the list I was looping over inside the loop itself. Like, I'd have a list of numbers and try to remove some while the loop was still going through it. My mentor in a free online study group finally pointed it out last Tuesday. He said, 'You're editing the book while you're reading it.' The fix is to make a copy of the list first or loop over a copy. It seems obvious now, but it tripped me up for weeks. Has anyone else run into this specific loop problem when they were starting out?

Serious question, everyone pushes Python but I went with JavaScript for my first language

All the guides and my friends said to start with Python because it's easier... but I wanted to build things I could see right in my browser. So I picked JavaScript and spent the last 3 months on freeCodeCamp. It was tough at first with all the curly braces, but now I can make a simple interactive quiz. Does anyone else think the 'start with Python' rule isn't right for everyone?

Just realized I wasted $300 on a coding bootcamp that taught me nothing

I signed up for a 'full stack in 12 weeks' bootcamp last year, thinking it was the fast track. They promised job help and real projects. The first month was okay, but then they rushed through React and backend stuff so fast I couldn't keep up. The 'projects' were just copying code from a video, and the job help was a list of links to apply on your own. After the 12 weeks, I knew less than when I started because I was so confused. I'm back to learning on my own with free stuff online and it's way better. Has anyone else had a bad bootcamp experience and found a better way to learn?

My Python script printed a number I didn't tell it to

I wrote a loop to count from 1 to 10, but it printed 11 at the end. I learned my condition was 'less than or equal to' instead of just 'less than'. Anyone else get tripped up by loop boundaries like that?

A friend insisted I start with C++ because it's 'real programming', but I found it just made me want to quit.

He said, 'If you can't handle pointers, you shouldn't code,' during a coffee chat in Denver, which pushed me toward Python and actually got me building things.

Just realized I've been teaching my nephew Python all wrong after seeing a kid's coding class at the library

I was at the downtown library yesterday and peeked into their free 'First Steps in Code' workshop for 10 year olds. They were using Scratch to make a cat chase a mouse, and every kid was laughing and totally focused. I've been trying to get my nephew to write 'Hello World' in a text editor for weeks and he just gets bored. Maybe starting with a visual block language is the better move? Has anyone else switched from a 'real' language to something like Scratch for a total beginner and seen it click faster?

Spent three hours yesterday because I forgot a single semicolon

I was writing a simple function in JavaScript to add two numbers together. Everything looked right, but the console kept throwing an 'unexpected token' error. I checked my brackets, my variable names, everything. I finally found it after scrolling line by line for way too long. I'd missed the semicolon at the end of the line where I declared the function. Anyone have a good trick for catching these tiny syntax mistakes faster?

I think everyone pushes Python too hard for total newbies

Last month, I was helping my friend in Chicago learn to code and started with Python like everyone says. We spent three hours just trying to get pip to install a simple library without errors, and he got so frustrated he almost quit. I switched gears and had him write a basic webpage with HTML and CSS instead, and seeing his own colorful page show up in the browser kept him going. Has anyone else found a different starting point that worked better?

My first Python script tried to print 'Hello World' 100 times and crashed my browser

I was following a tutorial that said to use a simple loop, but I accidentally wrote it to run forever instead of stopping at 100. I learned to always double-check my loop conditions before hitting run. Has anyone else had a simple script go totally wrong like that?

Spent 6 hours on a missing semicolon in my first JavaScript project

I was building a simple to-do list app, following a guide from a site called FreeCodeCamp. Everything looked right, but the 'add task' button just would not work. I checked the logic, the event listener, everything. I even rewrote the function three times from scratch. Finally, after almost a full day, I spotted it: a missing semicolon on line 47. The console error was not helpful at all. It just said 'unexpected token'. Has anyone else lost a huge chunk of time to a tiny syntax error like that when starting out?

My first program ran 42 times before I noticed the typo

I was trying to make a simple loop in Python last week, just to print numbers from 1 to 10. I accidentally typed 'range(42)' instead of 'range(10)' and walked away. Came back to my terminal in Seattle just scrolling the same numbers over and over. It was my first time hitting a number that big in my own code, even if it was a mistake. Anyone else have a silly bug that made you learn something basic the hard way?

I put a semicolon in the wrong spot in my Python script and it ran anyway

A guy at the library told me to skip the basics and it messed me up for months

He said, 'Just start with a framework, the fundamentals are a waste of time,' so I tried to jump into React without knowing plain JavaScript. I spent six weeks totally lost before I went back and learned variables and loops properly. Has anyone else had someone give them bad advice that set them back?

My 10 year old nephew asked me why my code was so 'shouty'

I was showing him a simple Python script I wrote, and he pointed at all the capital letters in my variable names and said, 'Why is it yelling at me?' I was using SCREAMING_SNAKE_CASE for constants, which is a standard thing, but hearing it from a kid made it sound completely silly. Has anyone else had a simple question make you question a basic coding habit?

TIL Python's 'for' loops are way easier for new coders than 'while' loops.

Tried teaching my kid both last week, and the 'while' loop with its manual counter just confused them. The 'for' loop with 'range(5)' clicked instantly because it handles the counting for you. Anyone else find beginners get stuck on 'while' loops?

Unpopular opinion: I was wrong about needing to start with Python

Everyone in my local library's beginner group last fall said Python was the only way to start. I tried it for about three weeks and felt like I was just copying code without understanding how anything actually worked. I switched to a free online C course instead, and writing 'Hello World' with a main function and seeing the compile process step-by-step made the concepts click for me. Has anyone else found a supposedly 'harder' first language actually made more sense?

My first real project crashed and I learned more in a day than a month of tutorials

I spent three weeks building a simple weather app using Python and a free API. Everything worked fine until Tuesday, when I tried to add a feature to save past searches. My code broke completely, showing a 'KeyError' I didn't understand. I spent over six hours reading error logs and checking a forum, which felt awful. Finally, I realized I was trying to access data from the API before it had fully loaded. That one mistake taught me about asynchronous calls and debugging. Has anyone else had a project fall apart and learned something big from it?

Unpopular opinion: I started learning Python by making a dumb text game about my cat

I was stuck on tutorials for a month, so I just opened a file and tried to code a game where my cat, Mr. Whiskers, hunts for treats. Figuring out how to make a simple 'if/else' choice work for that was way better than any lesson. What's a weird little project that actually helped you get a concept to click?

My simple Python loop printed the same number 100 times instead of counting up

I wrote a basic for loop to print numbers from 1 to 100, but I accidentally used 'range(100)' inside the loop itself instead of as the condition. It just printed the number 100 over and over. What's the right way to set up a counting loop so this doesn't happen?

I kept messing up my loops until I started drawing them out on paper first

I was trying to write a simple program to count from 1 to 100 and print only the even numbers, but my code kept skipping numbers or running forever. After getting frustrated for about an hour, I grabbed a notebook and physically drew boxes for the variables and arrows for the loop flow. Seeing it on paper made it click that my increment was in the wrong place. I rewrote the for loop in Python and it worked perfectly on the first try. Has anyone else found that stepping away from the screen to sketch things out helps untangle logic problems?

I thought 'pair programming' was just a silly buzzword until I tried it.

My friend and I were stuck on a Python function for two hours, so we screenshared on Discord and talked it through. We fixed the bug in like 15 minutes because he spotted a missing colon I'd looked at a dozen times. Has anyone else had a moment where a coding technique you doubted actually saved you?