c/coding-for-beginners

Had to choose between spaces and tabs for my first project. Picked wrong.

I was starting my first real Python project last week, a simple calculator app, and I ran into the whole spaces vs tabs debate. I went with tabs cause they seemed easier to type, just one key press you know. But then I shared my code on a forum and got roasted for 3 days straight because the editor messed up the formatting on every reply. I ended up spending an hour converting everything to 4 spaces. Has anyone else made a rookie choice that blew up in their face like that?

Tried using CSS Grid over Flexbox for my first real layout project

I've been messing around with HTML and CSS for about two months now, mostly following tutorials. Last weekend I finally built a simple portfolio page from scratch. I started with Flexbox because that's what all the beginner courses teach, and it worked okay for the header and nav. But when I got to the main content section with three columns and a sidebar, I spent like 4 hours trying to get the spacing right with margins and wrapping. Almost gave up, then a buddy from a coding meetup in Austin told me to try CSS Grid instead. Set it up in 15 minutes, no joke. Grid is way more intuitive for laying out pages in rows and columns, and I didn't have to mess with any hacks. Has anyone else found that Grid clicks faster once you get past the basic tutorials?

Just realized I could debug with print statements after 3 weeks of struggling

I was about 3 weeks into learning Python and hitting a wall with this loop that just would not work. Overheard my buddy's kid who's in high school say 'just print everything' on a call. I tried printing my variables step by step and spotted my typo in like 10 minutes. Has anyone else had that moment where the simplest fix was staring you right in the face?

Hit 100 lines of code for the first time and it actually worked

I've been learning Python for about a month and finally wrote something that wasn't just 'hello world' or a calculator. It was a little script that sorts my downloads folder by file type. Took me like 3 evenings to get it right. Felt pretty good when it ran without errors. Anyone remember their first real project that actually did something useful?

VS Code vs Sublime Text for a complete newbie - one is way better

I spent my first 3 months learning Python in Sublime Text because my friend said it was 'faster'. But I kept getting stuck on simple stuff like debugging and auto-complete. Then I switched to VS Code and it felt like cheating - everything just worked out of the box. The built-in terminal and extensions made it so much easier to spot my typos and run code. For a beginner, VS Code is clearly the better choice even if it uses more memory. Has anyone else found that the 'minimalist' editors are actually harder for learning?

Question about learning Python vs JavaScript for complete beginners

I spent 3 weeks trying to learn JavaScript first and kept getting stuck on weird stuff like callbacks and this keyword, then switched to Python and made a working number guessing game in 2 days. Python just felt cleaner and more like normal English you know? Has anyone else found that one language just clicked way faster than another when you were starting out?

Overheard a senior dev say she still looks up basic syntax on Google every day

That made me feel way less stupid about needing to check how to write a for loop for the third time this week, has anyone else felt that imposter syndrome fade after hearing pros admit the same?

Switched from console.log to the debugger tool and wow what a difference

Honestly I spent my first 6 months learning JavaScript just using console.log for everything. It worked but I was spending like 30 minutes on each bug just guessing where stuff broke. Two weeks ago I finally learned how to use the built in debugger in VS Code with breakpoints and step through my code. Now I can see exactly what each variable holds at every line in like 5 minutes. It feels like cheating compared to how I used to do it. Has anyone else avoided the debugger for way too long and then regretted it?

My first Python script deleted my whole downloads folder

I was sitting in a coffee shop on Main Street trying to follow a tutorial on file management. Accidentally used os.remove() in a loop without testing it first and watched 300 files disappear in about 2 seconds. Anyone else ruin something important when they were learning?

Why does nobody talk about version control for solo projects

I spent about six months building a little weather app on my own last year. Never used Git or any version control because I figured it was only for teams working together on big codebases. Then one afternoon I made a tiny change to my main file, saved it, and immediately realized I had broken everything. I spent almost two hours trying to undo what I did, with no backup and no way to go back. That frustration finally pushed me to watch a beginner Git tutorial at 11 PM on a Wednesday night. Now I commit my code every 20 minutes or so, even if nobody else will ever see it. Has anyone else had that moment where they wished they started using version control way earlier?

Doubts about pair programming got crushed after 2 months at a dev shop

I used to think pair programming was just a waste of time for beginners, like having someone watch you type. Then I got stuck on a React bug for 3 hours at a small shop in Austin, and my senior sat down and walked me through the logic in 20 minutes. Now I actually look for pairing sessions because the quick fixes teach me more than tutorials ever do. Has anyone else flipped their opinion on a coding practice they were sure was useless?

I finally get why some people swear by learning HTML before jumping into Python

My buddy Dave who codes for a bank told me last weekend that starting with Python made me skip over all the little logic steps HTML forces you to figure out, and now I'm wondering if beginners should go through the boring markup stuff first or just dive into the more practical languages like JavaScript or Python for faster results - what's your take?

Shoutout to the person who showed me how to use Git branches properly

I used to just code everything on the main branch and hope nothing broke. Then this guy in a Discord server spent 20 minutes walking me through creating feature branches and merging them. That was about 6 months ago and I haven't looked back. Now I can mess around with new ideas without worrying about ruining my working project. It took me like 3 tries to get the hang of it but now it feels natural. Has anyone else had a moment where one simple tip changed how you code?

Went to a local coding meetup last Tuesday and noticed everyone was learning Python but nobody knew Git

The room had 30 people all writing loops but when I asked how they merge branches, only 2 people raised their hands, so has anyone else found that beginners skip version control until it's way too late?

That free code editor I used for a year finally crashed and took my project with it.

I was using Notepad++ for my first Python projects because it was simple and free. Last Tuesday it froze up and deleted my whole 300-line calculator script when I force closed it. Has anyone else lost work to a basic text editor and switched to something like VS Code or PyCharm?

Lost 3 hours of work because I forgot to save before a git rebase

Was at my kitchen table at 2am trying to clean up some commit history on my first real project. Typed git rebase -i HEAD~5 and thought I knew what I was doing. Hit save and exit and boom - merge conflicts everywhere. Panicked and did git checkout . to 'fix' it and lost every change from the last 3 sessions. Didn't have any branches to fall back on. My buddy on Discord told me about git reflog the next day but by then the damage was done. Anyone else destroy their own code trying to be fancy with git?

Found a weird debug trick that saved my project

I was stuck on a bug for like 3 hours where my loop kept crashing. Turns out I had a typo in a variable name that Python wasn't catching until runtime. I started adding print statements after every line and finally spotted the mismatch. The trick was to print the exact variable type with type() before the crash happened. Has anyone else found a simple habit that catches these stupid mistakes?

Used to copy-paste code from Stack Overflow blindly. Now I actually read the docs first.

Last year I was building a simple login form. Grabbed the first snippet I saw. It worked but I had no idea how. Six months later I needed to add password reset. The snippet broke everything. Now I open MDN or the library docs, read the basics, then write it myself. Got stuck on async await last week. Same approach. Worked way faster. Has anyone else found that reading docs saves you more time in the long run?

Tried pair programming for the first time last Tuesday and it actually caught bugs I would have missed for hours

I always thought coding alone was faster but my buddy showed me how two pairs of eyes catch the silly mistakes like forgetting to close a tag, and now I'm wondering if I should do it for every tricky function.

Spent 45 minutes debugging a missing semicolon in my JavaScript yesterday

I was staring at this function that kept throwing errors, and it turned out I forgot one semicolon in a loop. Has anyone else spent way too long hunting tiny typos like this?

Chat with a barista in Portland made me rethink how I learn code

I was in line at a coffee shop last Tuesday and this barista told me she learned Python by breaking other people's projects on GitHub. Not like maliciously but forking repos and seeing what errors popped up. It hit different because I've been stuck watching tutorials for months and she learned more in 6 weeks of just poking around. Has anyone else tried learning by intentionally breaking code or is that a weird way to start?

Just realized my code comments were useless after a senior dev read them out loud

I was putting comments like 'this loops through the array' on every single line. Last Tuesday a senior dev pulled me aside and read three of them back to me, then asked 'what does this actually do?' Now I write comments explaining why I did something weird, not what the code already says. Has anyone else had their comment style wrecked by one specific piece of feedback?

Just found out my "Hello World" was actually wrong for 2 months

Thought spaced repetition was overhyped until my Python cert exam

I kept seeing people push Anki for memorizing code syntax and kept brushing it off. Figured it was just another productivity gimmick from the YouTube crowd. Then I failed a mock exam for the PCEP certification by 3 points because I kept mixing up list vs dict methods. Spent 2 weeks doing daily Anki cards for exactly those trouble spots and passed the real exam by a solid margin. Has anyone else found a specific memorization tool that actually stuck for learning syntax?

I spent a whole weekend on a CSS flexbox layout and it broke on mobile

I was sitting at my kitchen table last Saturday trying to get a simple three-column layout to stack right on phones. I followed every tutorial and copied code from Stack Overflow, but it kept overlapping on my Pixel 5 screen. After 6 hours of messing with margins and flex properties, I finally realized I forgot to add the viewport meta tag in the HTML head. Once I put that in, everything snapped into place in about 2 minutes. It made me think that beginners like me should check the basics first instead of jumping into complex fixes. Has anyone else wasted a bunch of time on something this tiny before?