c/coding-for-beginners

Just realized using a rubber duck actually works for debugging

I was stuck on this one little bug for like 2 hours last Tuesday. It was a simple HTML form that kept breaking when I submitted it. I tried checking the console, looking at my code line by line, even asked my buddy who knows way more JavaScript than me. Nothing was working and I was about to just give up. Then I remembered someone in a tutorial mentioned talking to a rubber duck. I grabbed this old rubber duck I got from a carnival years ago and just started explaining my code out loud to it. Halfway through describing what the submit button was supposed to do, I realized I forgot to add an event listener to the form itself. Soon as I fixed that, everything worked. Has anyone else had that moment where you explain your code to something dumb and suddenly see the answer?

Showerthought: I was wrong about Python over JavaScript for my first project...

I spent 3 months learning JavaScript for a personal site and kept getting stuck on async stuff... then my buddy said 'just try Python for the backend logic' and I finally got why simplicity matters. Has anyone else switched languages midway and felt like they wasted time?

Debate: Should beginners start with Python or JavaScript for their first language?

I learned Python first and it made loops and logic click instantly, but my friend started with JS and says building websites kept them motivated way longer than my boring console games so which approach actually teaches coding better for a total newbie?

Stuck between Python and JavaScript as my first language - what did you pick?

I started learning to code 3 weeks ago and hit a wall choosing between Python and JavaScript. Python seemed cleaner but JavaScript lets you build websites right away, so I went with JS and made a simple to-do list app. It took me 4 days to fix a stupid bug where my buttons didn't work because I forgot to load the script tag properly. For those of you who started recently, which language did you pick first and did you regret it or stick with it?

One comment from a senior dev made me rethink my whole approach to debugging

I was stuck on a bug for 3 hours last week. A guy I sit next to at the coworking space downtown asked me what I was working on. I told him about it and he just said "have you checked the order of operations in your if statement?" I blew him off at first because it seemed too simple. But after I tried it, that was the problem. He told me he starts every debugging session by looking at the easiest things first, not the most likely things. It clicked for me because I always dive into the complex stuff. Has anyone else had a simple tip from someone that completely changed how you code?

Someone told me my code was 'too clever' and it stung but they were right

I was trying to impress my study group by using list comprehensions and lambda functions everywhere until one guy said it looked like I was showing off instead of just solving the problem. I rewrote that Python script with simple for loops and if statements, and it actually made more sense to me a week later when I looked back at it. Has anyone else had to dial back their code to make it readable?

Vent: I realized I was building websites all wrong after a senior dev looked at my code for 30 seconds

Turns out nesting everything inside divs instead of using semantic HTML was making my sites impossible for screen readers to navigate, and it took a coworker reading my code out loud for me to finally get it. Has anyone else had a moment where something basic you skipped over came back to bite you?

Watched a guy debug his code with a notebook at the library and it changed my whole approach

I was at the main branch on a Tuesday afternoon and saw someone writing out each variable by hand on graph paper before typing a single line, and I tried it the next day and caught three bugs I would have missed, has anyone else gone back to pen and paper for coding?

Shoutout to the guy who told me to stop nesting my CSS so deep

I was building a simple landing page and had like 6 levels of divs inside each other. Some guy on Reddit told me I was making a nightmare for myself and to use BEM naming instead. He said something like 'your browser is crying trying to figure out which .content div you mean.' I swapped to block-element-modifier class names and cut my stylesheet from 400 lines to 200 lines in about 2 hours. Now I can actually find what I need to edit without scrolling forever. Has anyone else had a random comment from a stranger totally rewire how you code?

My coworker told me to stop using brute force for loops in Python, I ignored him for 3 months

My senior dev kept saying 'just use list comprehension, trust me' and I kept thinking it was a waste of time to rewrite working code. Then last week I ran a script that took 45 seconds to process 10,000 records and he showed me how to cut it to 2 seconds with one line. Has anyone else dodged a basic optimization tip for way too long and then felt dumb when they finally tried it?

Found out I was nesting divs wrong for 6 months

I kept wondering why my layouts looked off center and weird. Turns out I was putting block elements inside inline elements without thinking about it. A guy on StackOverflow pointed it out and showed me the HTML spec from 2014. Has anyone else had a basic CSS rule click way later than it should have?

My first React app broke in 5 minutes on production

I spent 3 weeks building a little todo app in React for my portfolio. Deployed it to Netlify last Thursday and it crashed the second someone tried to add a task. Turns out I forgot to handle the case where localStorage is full or disabled. My error handling was just a console.log and a prayer. Did anyone else learn error handling the hard way after pushing to production? What do you actually check before you hit deploy?

Saw my first real code from 7 months ago... oof

My coworker told me my code was 'too clever' and I finally got it

She said readability matters more than showing off with one-liners, and she was right. I went back to a project from 3 months ago and couldn't even follow my own logic. Has anyone else had to unlearn bad habits from trying to look smart?

Vent: My code worked fine until I pushed it to production last night

Had a simple PHP form that collected email signups. Tested it locally maybe 10 times, all good. Pushed it to the live server around 9pm and woke up to 400 error reports this morning. Turns out I forgot to change the database connection string from localhost to the actual server. Rookie mistake but I've been coding for 6 months now so that stings. Anyone else have a deploy fail because of something this dumb?

My first Python script broke the whole team's database during a demo

I was showing off my automated report tool to my coding group last Tuesday, and it accidentally dropped a whole table instead of just reading from it. Turns out I had a single wrong line where I used `DROP` instead of `SELECT` in a test query - rookie mistake, I know. Has anyone else had a simple typo turn into a bigger mess than expected?

Thought I could skip version control for solo projects but lost a week of work after a bad refactor

Rolled back an experiment in my personal site project and accidentally wiped two days of updates because I wasn't committing, so now I'm curious if anyone else learned this lesson the hard way or am I just stubborn?

TIL I hit 1000 lines of code in my first project and it actually compiled

Honestly, I started learning Python like 2 months ago just for fun between shifts. I was working on this little calculator thing and accidentally hit 1000 lines of code without realizing it. Ngl, I was surprised because I thought I'd mess up way earlier with all the math logic. When I ran it and it actually worked without errors, I felt like a total boss for a minute. Has anyone else hit a random milestone like that and felt weirdly proud of it? Like how did you even track your progress?

That one Wednesday in March where my code actually compiled on the first try

I had been banging my head against a Python script for two weeks, and one random Wednesday after school it worked perfectly on the first run with zero errors. My students thought I was losing it when I started laughing at my desk. Has anyone else had that weird day where everything just clicks for no obvious reason?

Spent 4 hours debugging a missing semicolon in JavaScript yesterday

I was working on a simple calculator project for my coding class and the whole thing just refused to run. It took me until 11 PM to realize I forgot a semicolon on line 47 of my script.js file. Has anyone else spent way too long hunting down a tiny typo like that?

Just realized that VS Code extension I ignored for months actually saves me an hour a day

I've been writing code for like 6 months now and kept seeing everyone talk about this Prettier extension for formatting code. I thought it was just some fancy tool for people who are too lazy to hit tab or space their stuff out. Then last week I was working on a project with like 15 files and kept messing up brackets and indentation. Finally installed Prettier and it just fixed everything in one click. I wasted so much time manually aligning stuff. Has anyone else fought against a tool forever then finally gave in and realized it was actually useful?

Switched from YouTube tutorials to official docs and wow what a difference

Spent 3 weeks on a Python project using random video tutorials. Kept getting stuck on weird errors. Finally opened the official Python docs. Everything made sense in 2 days. The docs explained the logic, not just copy-paste steps. Has anyone else found official docs easier than videos?

Found a bug in my code that was hiding for 3 weeks

I was working on this little calculator app for my portfolio and kept getting wrong totals on one specific input. Tried everything, rewrote functions, checked my math like a dozen times. Finally yesterday I printed out the whole script on paper and went through it line by line. Turns out I had a typo in a variable name from like 3 weeks ago. I used 'userInpit' instead of 'userInput' and the compiler never even told me because the misspelled one was just undefined. So my code was just skipping that line silently the whole time. Felt like a dummy but also it was kinda cool to figure out. Has anyone else had a bug that was literally just a single wrong letter?

Tried learning React first and it was a total mistake

Everyone online kept saying start with React because there are more jobs. I spent 3 months on it and got nowhere. The JSX syntax and state management just broke my brain every time. So I stepped back and learned plain JavaScript for 6 weeks straight. Now React actually makes sense because I understand the basics underneath. I think the popular advice to jump straight into frameworks is hurting beginners. Has anyone else hit a wall with React and had to go back to basics?

PSA: That free code bootcamp meetup in Denver last month changed how I learn

A guy running the session showed us how to break a hard problem into 15 minute chunks using a timer. Has anyone else tried timeboxing for learning Python or is it just me?