I've always believed that the best way to learn is by doing. So, when I got the opportunity to join the Keploy API Fellowship, I jumped right in! I'm thrilled to share that my journey has officially begun, and it’s already been an incredible learning experience.
For those who might not know, Keploy is an open-source tool that creates E2E tests and stubs from API calls, essentially making testing faster and more efficient for developers. The Keploy API Fellowship is a program designed to mentor and guide developers into the world of APIs and open-source contributions.
Our first session, "Open Source 101," was the perfect kickoff. It was a masterclass in the fundamentals of open source, Git, and GitHub. It demystified the process and showed us how accessible contributing to open source can be.
Now, with that knowledge under my belt, it's time to get my hands dirty with our first official assignment!
🚀 The First Mission: From Theory to Practice
The first assignment is cleverly designed to build our foundation and confidence. It’s broken down into three key tasks:
- Task 1: Building My Digital Storefront - The GitHub Profile README
The first challenge is to create a standout GitHub Profile README. This isn't just about listing skills; it's about crafting a narrative. A good README is your personal billboard in the developer world. It’s a chance to showcase your projects, highlight your achievements, and let your personality shine through. I’m genuinely excited to polish mine and create a profile that truly represents my journey and aspirations as a developer.
You can check my GitHub profile here
- Task 2: Making My Mark - My First Open-Source Contribution
This is the task I’m most excited about: making a real contribution to an open-source project by submitting a Pull Request (PR). The beauty of how Keploy has structured this is the sheer variety of options available. They have a whole list of active projects, from their core Go repository to collections of public APIs, documentation, and code samples in various languages like Python, Java, and TypeScript.
This inclusive approach means everyone can contribute, regardless of their comfort level with coding. You can fix a typo, add to a list of engineering prompts, or tackle a labeled issue. The core message is clear: every contribution matters. I’ve decided to start by adding some valuable public APIs to the Keploy Public APIs Collection to get my feet wet in the contribution process.
- Task 3: Sharing the Journey & Building in Public!
This final, optional task is all about community and transparency. We're encouraged to share what we've learned through a social media post or a blog (like this one!). It’s a fantastic way to practice "building in public," a concept I'm a huge fan of. It helps solidify your learning, connects you with the wider tech community, and documents your progress.
Plus, Keploy is offering some awesome goodies for the best posts! Who doesn't love a bit of swag? 😉
Why This Fellowship is a Game-Changer
What's already clear to me is that the Keploy API Fellowship isn't just another online course. It’s a hands-on, community-driven experience. The emphasis on practical application and the supportive environment creates the perfect incubator for growth.
I’m so grateful to the Keploy team for putting together such a thoughtful and impactful program. This is just the beginning, and I’m incredibly excited to see where this journey takes me, the skills I’ll gain, and the contributions I’ll make.
Stay tuned for more updates!
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.