DEV Community

M
M

Posted on

Day 0. Getting Back to Basics

just a pic
Today I decided to start digging into the materials of a Data Engineering course. Really hoping to turn this summer into my own personal coding bootcamp.  


📚 About Resources... 

I enrolled in a DE course about two years ago. Back then, it felt overwhelming — probably because I lacked context. Since then, I’ve tinkered with Docker, Git, Bash, and solved a few problems in C and Python. That’s the extent of my progress so far.  

My plan? Combine the course with open resources like DE ZoomCamp. I also want to try the LLM ZoomCamp — apparently, RAG is that tech I wanted to learn but didn't know its name. Heh.


🔍 Findings of the Day...

  • Turns out, my API knowledge is… nonexistent. Who knew there was more to APIs than just REST? 😴😅

  • I still second-guess myself in basic Python sometimes...  

For example, this question tripped me up earlier. I didn’t have an interpreter at hand, so I went with intuition. Surprisingly, my intuition was right.

Q: Is this code valid?

  

class demo(list):
    def __test__(self, key):
        return []
a = demo()
a['test'] = 7
print(a)

Enter fullscreen mode Exit fullscreen mode


  

Still believe that coding is often an experimental science: you learn by running code.


💡 Some other observations...

Compared namespace vs. scope today. They’re both about name visibility, but:  

  • Namespaces are explicit containers (to avoid conflicts).  

  • Scopes are implicit, tied to code blocks (where a name is accessible).  


⚙️ Plans for tomorrow

Still wrestling with my environment setup — nothing feels quite right yet.

Maybe tomorrow I'll do something about it finally and will be able to complete more than just a few random coding questions in Google Colab. 

Top comments (0)