Abhijeet Kadam

I came into software sideways. An Electronics and Telecommunications degree left me more curious about the code running on the hardware than the hardware itself, so I taught myself the rest by building things instead of waiting for a course to explain them.

What pulls me in is the boundary where my code has to trust something it doesn't control: a phone carrier, an email server, a model that might just make things up. Getting that boundary to behave predictably is most of what I find interesting about this job.

I'd rather spend a weekend breaking something on my own project than get it right in a tutorial. That instinct is basically my whole resume.

Still convinced a well-placed console.log beats a debugger, and that the best compliment a system can get is nobody ever had to think about it.