Code Whisperer

When I finally fell in love with Godot, I realized it taught me a valuable lessons:

• You can’t learn alone, community is necessary when learning something new.
• It's better to go slow and consistently than sprint and risk burn out
• Reading documentation is important

That last one hit hardest. It felt like a punch to the gut. See, the community can help, but if you’re getting stuck on things that are clearly in the official docs, the problem’s on you. You’re not reading enough. That realization set me off on a new path – books. My game, Chaotic Summoner, tanked, and I knew exactly why. I was in love with creating and learning as I went, but there’s a difference between figuring things out on the fly and knowing the craft. Best practices? Hidden away in university textbooks I never touched. So, I started reading. Diving into knowledge I never had. Sure, it took time away from big projects, but in return, I got a deeper understanding and more control over what I created.
Now, I’m on a journey. One step at a time. I’m becoming the Code Whisperer. Sure, people around me might laugh at the idea, especially with AI taking over. But for me, settling down into something that isn’t my true passion? That’s the dumbest idea of all. “I’m gonna make games one day.” I said.
“No, you won’t. You don't even know how to say to computer - make the character jump.”
“I do! *Yoomp!*”
Fast forward. I pursued IT in university, until electronics class. I hated it, so I dropped out and became a CNC programmer instead. I was pretty happy. Then I met another Dan at work. A menace who cracked networks for fun and got me into Linux. He tore apart my safe space, pushed me, shared pranks with me, opened up to me and then one day, he left. He did it, he scored a job in penetration testing.
I was alone again and my mind was racing: "Python, Python..."
So I started and I never stopped.