DEV Community

Cover image for Why I Stopped Watching Tutorials and Started Breaking ThingsπŸ˜ˆπŸ’£πŸ’₯
Maame Afua A. P. Fordjour
Maame Afua A. P. Fordjour

Posted on

Why I Stopped Watching Tutorials and Started Breaking ThingsπŸ˜ˆπŸ’£πŸ’₯

You know the feeling. 😩

You just finished a 4-hour "Python Zero to Hero" video. You followed every keystroke. You built the To-Do List app. You feel productive. You feel like a programmer. πŸ¦Έβ€β™‚οΈ

Then, you open a blank file to try and build something simple on your own... and your mind goes completely blank. 😢

The blinking cursor mocks you. 😈

For the longest time (and even now {sike!}), I was stuck in this loop. I call it the "Illusion of Competence." 🎭 I wasn't learning how to solve problems; I was learning how to type what someone else had already solved.

I realized that in the real world, there is no tutorial for the specific bug crashing production at 3 AM. ⏰πŸ”₯

So, I decided to change my strategy. I stopped trying to be perfect, and I started trying to break things. πŸ”¨

Here is how I changed my workflow.

1. The "Delete One Line" Rule 🧱

Now, when I look at example code (whether it's from a lecture or a tutorial), I don't just copy it. I play "Jenga" with it.

I delete a line. βœ‚οΈ I change a variable type. πŸ”„ I remove a colon. ❌

I want to see the error message. I want to know exactly what happens when the code breaks. In the past, red text in the terminal scared me. 😱 Now, I realize that error messages are just the compiler trying to communicate with me. πŸ—£οΈ

If you don't know what a specific error looks like, how will you know how to fix it later? πŸ€·β€β™‚οΈ

2. Embracing the "Ugly" Code πŸ§Ÿβ€β™‚οΈ

Tutorial code is always clean. Student code is usually messy. And that is okay. πŸ‘Œ

I used to obsess over writing "Pythonic" code before I even got the script running. Now, my goal is just to make it work. Even if it’s ugly. Even if it’s slow. 🐒

If I can make it work, I can refine it later. But you can't refactor code that doesn't exist. πŸ’‘

The Takeaway πŸš€

If you are like me, feeling overwhelmed by the sheer amount of tools we need to learn (Docker 🐳, Kubernetes ☸️, AWS ☁️, Python 🐍...), take a deep breath. πŸ§˜β€β™‚οΈ

Close the 10-hour tutorial. Open a blank file. Write some terrible code. Break it. Fix it.

That is where the real engineering happens. πŸ—οΈ

Top comments (6)

Collapse
Β 
mezieb profile image
Okoro chimezie bright β€’ β€’ Edited

Thanks for sharing you just nailed it in reality fixing bug is our companion,we are glad you have discovered the trick and now rock it to the top

Collapse
Β 
maame-codes profile image
Maame Afua A. P. Fordjour β€’

Glad you liked it ! 😊

Collapse
Β 
maame-codes profile image
Maame Afua A. P. Fordjour β€’

You are welcome!

Collapse
Β 
nafisahbadmos profile image
nafisah badmos β€’

Definitely a good idea! Infact I am embracing it ASAP, thank you!

Collapse
Β 
maame-codes profile image
Maame Afua A. P. Fordjour β€’

You are welcome>😊