|
I mostly learn by breaking things, then figuring out why they broke. That habit has taken me through full stack apps, a few MVPs, some cloud experiments that failed before they worked, and a growing list of open source repos, some I built from scratch, some I just showed up and contributed to. Give me a codebase I've never seen before and I'll happily spend a weekend finding my way around it. Not because it's easy. Because that's usually how I actually learn something. |
$ ./about-me.sh [+] exploring codebases [+] breaking things [+] debugging [+] understanding why [+] building again $ git status On branch learning STATUS=STILL_BUILDING |
I did Google Code-in back in 2018, completed 6 tasks, and ended up with a certificate and a Google t-shirt for it. Then I didn't touch open source again for six years. Picked it back up in January 2026, first on my own, then through GSSoC and ECSOC.
|
|
flowchart LR
A["🌱 2018<br/><b>Google Code-in</b><br/>6 tasks · certificate + t-shirt"]
B["⏸️ 2019 → 2025<br/><b>Went quiet</b>"]
C["💻 Jan → Apr 2026<br/><b>Started again, solo</b><br/>5 repos"]
D["🤝 May 15 → Aug 15 2026<br/><b>GSSoC '26</b><br/>Contributor"]
E["🚀 Jul 2026 → Now<br/><b>ECSOC 2026</b><br/>Project Admin · LearnHub"]
A --> B
B --> C
C --> D
D --> E
classDef first fill:#2563EB,stroke:#60A5FA,color:#FFFFFF,stroke-width:2px
classDef pause fill:#475569,stroke:#94A3B8,color:#FFFFFF,stroke-width:2px
classDef self fill:#7C3AED,stroke:#A78BFA,color:#FFFFFF,stroke-width:2px
classDef gssoc fill:#DB2777,stroke:#F472B6,color:#FFFFFF,stroke-width:2px
classDef ecsoc fill:#059669,stroke:#34D399,color:#FFFFFF,stroke-width:2px
class A first
class B pause
class C self
class D gssoc
class E ecsoc
linkStyle default stroke:#64748B,stroke-width:3px
|
An open source learning platform I run as project admin, handling issues, PRs, and contributor onboarding. |
Verifies academic credentials so no one has to call a university registrar to check if a degree is real. |
A MERN app for running campus events without ten WhatsApp groups and a lost Google Form. |
| Repository | What I worked on |
|---|---|
| 🃏 DevCard |
|
| 💓 CommitPulse |
|
| ⚙️ Telos Runtime |
|
| 🎪 Event Management System |
|
| 🔧 urBackend |
|
It starts with an idea, then I try to understand what I'm actually solving before I touch code. Then a rough prototype, usually ugly, usually broken in at least one place. Once it does the basic thing, it becomes an MVP. Testing finds the stuff I missed. Then I fix it and ship it, and if anyone else is using it, they tell me what's still broken. Repeat.
flowchart LR
A["💡 Idea"]
B["🔎 Understand"]
C["⚡ Prototype"]
D["🚀 MVP"]
E["🧪 Test"]
F["🔧 Improve"]
G["🌍 Ship"]
H["🤝 Contribute"]
A --> B
B --> C
C --> D
D --> E
E --> F
F --> G
G --> H
E -->|Needs work| F
G -->|Feedback| E
Building, contributing where I can be useful, and figuring the rest out as I go.
Build it. Break it. Fix it. Ship it. Do it again.