From failing JEE to making over ₹8.5 lakh through opensource in my first year of college. It all started with depression, failed JEE, and a breakup. I couldn’t face the man in the mirror anymore. So I decided to start over. My first 3 months of college were pretty basic some web dev, a little DSA, nothing crazy. Then around December, I discovered open source. For the next one month, I was mostly just f**king around. Made a few PRs, nothing significant. Then February changed things. 35 of my PRs got merged into Palisadoes Foundation I heard about Summer of Bitcoin. I filled the form only because my friend was filling it. Somehow, I cleared the first round. @kirat_tw told me, “Give it a try.” So I started working on both GSoC and SoB First Crash The GSoC Org where I had gotten 50+ PRs merged didn’t get selected for GSoC. Second crash: I submitted my SoB project ~30 seconds before the deadline. At that point, I genuinely thought I was out. I had to start GSoC all over again with different organizations. This time, I kept one as a backup. Luckily, I cleared the first level of SoB too. In the month of May. I got into the GSoC Org I had kept as my backup(God’s plan >>> your plan) a long-term project worth $3,000. Three days later, I got into SoB too and made another $3,000+. Two weeks after that, I got into @SuperteamIN's Superdevs program. Finished in the top 20 of the entire batch and won another $2,500. By the end of it, I had made ₹8.5L+ in my first year of college. And now, I’ve joined @TrenchersAI as an AI Engineer. If there’s one thing you should take from my story: AI won’t replace you. But someone who knows how to use AI might.

Sharing the proposals that got me selected for: → GSoC 2026 with CDLI (Search & Discovery Improvements) → Summer of Bitcoin 2026 with ContextVM (Rust SDK) github.com/harsh04044/propos… Hope this is useful for future applicants! #GSoC2027 #SummerOfBitcoin #OpenSource

Done.

Just a builder among builders 🛠️

A month into working at a startup, and I've learned more about shipping software than I expected. 115 issues done, and a lot learned along the way. Real bugs, real users, real trade-offs. The best part isn't the number, it's how much you learn when you're building and shipping real things. 🚀

After a long break from open source, reviewed a PR today 👀 Feels good to be back in the review cycle.

This guy shows you how to automate video creation with Claude Code in just 22 minutes. 👀

A Chinese developer built a tool that has crossed 42K GitHub stars 🔥 Reverse Engineering Anything (REA) integrates tools like Ghidra and Hopper with Claude Code and Codex, allowing AI agents to analyze software without access to its original source code. Interesting to see how AI is expanding what's possible in reverse engineering. 🔗 github.com/morluto/rea

25 skills to help AI agents write better code and follow better engineering practices. From TDD and security to code reviews and web performance. Compatible with Claude Code, Cursor, Codex and more. Worth checking out 👇 github.com/addyosmani/agent-…

Okay, this is REALLY cool. If you're into design.md, check this out 👇 styles.refero.design One of those websites that makes you want to redesign your entire project.

Meanwhile: @claudeai shipped this 7 months ago 💀

Today I realized that doing good work and navigating work are two completely different skills. And if you want to do well at work, you better get good at both.

Seeing people say: “I don’t know, AI wrote it.” is becoming way too common. If you ship it, it’s your work. AI can help you move faster, but you still have to understand what you’re shipping and be accountable when things go wrong.

I thought I was using AI. Turns out AI is using me. 💀

How I use AI for big coding tasks: I don't ask AI to “build the whole thing.” I use it as a loop: Plan → Decide → Build → Verify → Ship → Record AI moves the work forward. I stay in the loop for every important decision.

How to start contributing to open source? I get this question a lot. My advice: start by getting comfortable with Git and the PR cycle. Pick a project you’re interested in and start with small PRs. It’s completely okay if your first contributions are just UI fixes, documentation, typo fixes, etc. The goal initially isn’t to make huge contributions. It’s to get comfortable with the cycle: → Open a PR → Get reviews → Address feedback → Get it merged Once you’ve gone through this cycle a few times, you’ll automatically gain the confidence to take on bigger issues. Don’t wait until you “know enough” to start contributing. Start small, learn along the way, and keep shipping.