Arnay Shukla

I've learned to slow down before speeding up. Before I write code, I try to actually understand what's already there—the structure, the flow, the decisions someone made before me. I've rushed past this step enough times to know it usually costs more than it saves.

I prefer honest feedback over comfortable agreement. When I'm working with someone, I'd rather they poke holes in my thinking than nod along. I try to offer the same in return. It's not about being right—it's about getting it right, which is easier when you're not attached to your first idea.

I care about the whole system, not just the piece I'm touching. Partly because I've seen small fixes create strange problems elsewhere, and partly because it's just how my brain works—I need the context to feel grounded.

I try to be methodical. Not because I'm naturally disciplined, but because I've noticed that when I cut corners, I usually know I'm doing it. And knowing doesn't undo the shortcut. So I try to read before I write, verify before I assume, and think through the path before I start walking it.

I love mentoring juniors. I have experience building teams from scratch—I built a team of 6 engineers for a startup. I've mentored people at Nykaa, Allen, and Airtel Africa, and all my juniors have become some of my closest friends. They've also helped me work smarter by introducing me to new tools, technologies, and approaches. I've learned a lot from tech discussions with some of the smartest people I've known—my juniors.

I'm still learning. But this is how I try to work.