Coding workspace
Chapter 10 of 12The long, quiet work of coming back

Rebuilding Identity

The Full Story

After IndusianAssist collapsed, I found myself in a strange place. Not rock bottom — but hollowed out. The startup had consumed so much energy that when it ended, I realized I had let my core technical skills atrophy. I'd been managing people and clients, not writing code.

The identity crisis was real. Was I a developer? A founder? A manager? I didn't know. And without knowing who I was, I couldn't move forward.

The rebuild was slow and unglamorous. I returned to fundamentals. Picked up Flutter. Rebuilt systems from scratch. Found a mentor who didn't sugarcoat my gaps but showed me exactly how to close them. I spent months doing the invisible work — the kind that doesn't make for good social media content but makes for a more capable engineer.

Then I cleared UCA — a competitive assessment that matters in the engineering world I was trying to enter. It wasn't a trophy. It was proof of concept. Proof that I had actually rebuilt, not just claimed to.

Confidence, I learned, is not a feeling you wait for. It's a conclusion you earn through evidence.

Gallery
Timeline
Post-collapse

Technical skill gap identified — returned to fundamentals

6 months

Flutter, systems architecture, and mentorship

College final year

Cleared UCA — confidence rebuilt on evidence