Week 1 of GSoC: Learning Through Dependencies and Communication

My GSoC journey began with something most developers both respect and fear: dependency resolution. The first issue I picked involved fixing deprecated packages and aligning the project with the latest compatible versions. Sounds simple — but I quickly realized just how intricate and interconnected dependency management can be.

What I Learned during this week, I got a solid grasp of:

📦 How Flutter and Dart dependencies interact.

🔍 How to identify compatible versions and understand why upgrading isn't always the best solution.

🛠️ Refactoring deprecated components — such as replacing imageBuilder with a custom implementation.

🚀 Diving into CI/CD pipelines, understanding automated test workflows and how things work post-commit.

📁 Tools like FVM (Flutter Version Management), VIM, and GitHub’s advanced features.

🔐 An important insight: In production, we use .define to keep client secrets (like API keys or client IDs) safe — preventing leaks of sensitive tokens.

🔒 I also explored authorization concepts in more depth, including how tokens are managed securely on the client side.

🚀 I also got to know that in big companies like my org CircuitVerse, we don't work on the latest flutter version, but a bit older version.

Communication: The Real Game-Changer
One of my key reflections this week wasn’t just technical — it was personal.

Initially, I found myself struggling with communication. Not because the mentors weren’t supportive — in fact, they were incredibly helpful and available. It was more about me not reaching out enough or asking the right questions early on. Toward the end of the week, I made a conscious effort to change that and started communicating more proactively.

Special thanks to Hardik for being consistently patient and encouraging throughout this period.

Looking Ahead
In hindsight, I recognize that my initial solutions could have been more efficient. But this is part of the journey — learning by doing, improving with every iteration. From next week, I plan to:

Start with a more structured approach to issues.

Communicate early and clearly.

Document more of my learning as I go.

I’m excited for what’s ahead and grateful for this opportunity to grow through real-world, open-source experience. 💪