Pushkar Singhal

i've always believed that you don't truly understand a system until you've seen it break.

for me, programming started with a simple, destructive curiosity: what happens if i push this too far?

that curiosity evolved into a career centered on extreme optimization—building backends that are as elegant as they are resilient.

~ chapter 1: the breaking

my journey didn't happen in a classroom.

it happened in the quiet corners of my room—just another introvert student with a laptop and too many questions. while the world followed a syllabus, i was teaching myself the language of machines.

i didn't want to just use software. i wanted to understand why it worked, and more importantly, why it didn't.

this self-taught discipline instilled in me a unique approach to problem-solving: find the edge cases, understand the failure points, and then build something that can't be broken.

~ chapter 2: the rebuilding

i don't just write code; i ship optimizations.

my early work, like Tripsync and Agile, focused on breaking down monolithic ideas into highly performant microservices.

then i built CmdMesh. i wanted to break our dependency on the bloated, "noisy" modern web. it’s an AI-powered CLI that cuts the latency between thought and execution.

presently, i’m exploring AI security with DivyaDrishti—a deepfake detection system that restores integrity to our digital world by analyzing where AI fails.

~ chapter 3: the optimization

today, i work at Software Incubator.

working within a group of 30 people, i’ve moved from building individual projects to production-scale systems. the team here supported me when i was still finding my footing.

i remember when seeing a command prompt used to worry me. the terminal felt like a foreign space. today, that worry is gone. now, i feel i can build anything.

i now focus on the parts most people ignore: the background tasks, the edge cases, and the infrastructure that keeps the lights on. true optimization is building something so stable that it becomes invisible.

~ chapter 4: the philosophy

maintainable code is the ultimate form of optimization. i’m obsessed with building backends that can handle reality without breaking.

the best developers share their failures as much as their successes. don't tell me your title. show me how you fixed what was broken.