Loading…
29
Can we talk about the GUILT of using code snippets you don't GET?
When I was learning to code, I hit a wall with a Python script for sorting data. I found a solution on Stack Overflow that used a lambda function, something I hadn't learned yet. After pasting it in, it worked LIKE magic, but I felt LIKE a FRAUD because I didn't earn that fix. Everyone says to use resources, but where's the line between learning and just copying? I decided to study that lambda until it clicked, which took hours. Now I see it's a common beginner dilemma: you want to move forward, but you also want to understand EVERY step. It's a tricky balance for sure.
3 comments
Log in to join the discussion
Log In3 Comments
masoncooper7mo ago
Remember feeling that exact same way with CSS flexbox years ago. Honestly copied whole layouts without getting how they worked, which forced me to actually learn it later. That pressure to understand everything right away does fade as you keep going.
8
the_patricia7mo ago
The best flexbox lesson I ever got was from a 10-line layout I copied and then broke on purpose. I changed one justify-content value and watched my whole sidebar jump across the screen. That visual cause and effect stuck way harder than any tutorial. You stop being scared of the code when you see it react to your changes in real time. Breaking things to fix them is the fastest way to make the rules make sense.
7
susanh467mo ago
Oh man, @masoncooper, that hits home. I spent so long just copying flexbox code and praying it worked. Felt like a fraud until I finally broke enough stuff to get it.
2