Question about hitting 100 lines of code that actually works

So I finally got a small script to run without errors after about two weeks of trying. It was just a simple thing to sort a list of names, but I hit exactly 100 lines of code. Everyone says the number of lines doesn't matter, but seeing that triple-digit count in my editor felt like a real win. It wasn't about being fancy, it was about sticking with a problem long enough to make something that functioned. I had to look up loops, figure out how to compare strings, and debug a typo for an hour. That specific number made the abstract idea of 'learning to code' feel concrete for the first time. Has anyone else had a small, silly milestone that actually meant a lot when they were starting?

3 comments

3 Comments

troy_price1mo ago

Two weeks for a hundred lines is a real grind, but I get it. Honestly, the fact you spent an hour on a single typo is the most real part of this whole story (we've all been there). That specific number turning abstract learning into something you can see is a huge deal.

nelson.vera1mo ago

What's the biggest typo you ever lost time to?

finleyl391mo ago

My first working script was 47 lines and it took me three days to stop it from just printing "hello world" over and over. I had the print statement inside the loop by mistake. I felt so smart for fixing it, then realized I'd basically just deleted one line. That hundred-line mark is a real wall to break through.