Rahul Gupta’s Post

I’ve been thinking about something lately that not enough developers are talking about. For years, we’ve been pushing code to GitHub. Late nights, side projects, client work, experiments — all of it sitting there as a reflection of our journey as developers. We made it public to share, to learn, to collaborate. But now there’s a shift happening. A lot of that publicly available code is being used to train AI models. And in many cases, developers don’t even realize it’s happening. “Public” doesn’t really mean “free for any use,” but the lines are getting blurry. This isn’t about blaming platforms or stopping progress. AI is powerful and it’s here to stay. But as developers, we should at least be aware of how our work might be used — especially when it’s something we’ve spent years building. If this concerns you even a little, there are a few simple things you can do. Start by checking the license you’re using — not all licenses protect you in the same way. You can also add a note in your README making it clear that your code shouldn’t be used for AI training without permission. If something is truly important or sensitive, keeping it private is still the safest option. And it’s worth keeping an eye on policy updates from GitHub as things evolve. Open source has always been about sharing, but sharing shouldn’t mean losing control. We just need to be a little more intentional now. Curious to hear what others think about this — are you okay with your code being used to train AI? #AI #OpenSource #GitHub #Developers #MachineLearning #CodeOwnership #Tech #SoftwareDevelopment

Hi Rahul Gupta, I'm okay with it, nothing is safe. It's all about, how long you can hold it safe. If security does matters to you alot, you will found yourself creating one security system for yourself and how long will you able to maintain that too? Better to move with faith, things will align naturally.

Like
Reply

To view or add a comment, sign in

Explore content categories