OSS contributions have become a de facto metric for hiring engineers. Yet, marginalized developers are largely invisible in the OSS community. I’ll identify reasons one might be a “quiet developer”, and speak to how we can hire and empower these people while redefining community engagement entirely.
Trigger Warnings: discussion of workplace discrimination, mentions of physical and mental health
Open Source contributions are one of the most common de facto means to judging the competency of engineers, despite frequently resulting in the further marginalization of already marginalized people. In this talk, I’ll coin the term “Quiet Developer” for developers who are active, engaged, but to the eyes of many completely invisible for many reasons. I’ll dive into how developers like us survive, how hiring practices around us need to change, what employers can do to empower us, and in doing so finally chip away at the monolithic idea of “community engagement”, highlighting instead the many less-visible communities so many of us are part of.
I'm a Brooklyn-based front-end engineer working with MongoDB and focused on diversity and inclusion. As someone queer and neurodivergent, I spend a lot of time thinking about what inclusion actually means, and how we can leverage technical industries to improve the lives of minorities, through employment and through asking how we impact our surrounding communities both in the services we offer and in the resources we consume.
When I'm not at work coding, I'm a practicing watercolor artist, composer, and I play in a Javanese Gamelan based out of NYC.