My name's Nick (or qrush) and I've been an active Reddit user for more than 13 years now. I remember when the first subreddit (proggit!) was split off, have made it to the front page a few times, made long-lasting friends through local-based subreddits, and learned countless facts - mostly about cats. The various Ruby and Rails based subreddits helped me promote my open source project Gemcutter, which eventually turned into RubyGems.org. My career as a software engineer has grown in no small way thanks to Reddit, and I'm excited that there's now an opportunity to make an outsized impact as the Head of Reddit Developer Platform.
In my current role as Engineering Manager for Wistia's Platform team, I've been leading a team of 5- directly managing 3 senior software engineers along with a designer + quality engineer to build up internal tools, libraries, and shape the building blocks of how our services fit together. A big part of this work, and all my work throughout the years, has been a deep focus on APIs.
For example, I've been a big fan of GraphQL for a few years now, and I've championed its use at Wistia and my former company Chatterbug. Historically, I've tried to give at least one conference talk/year. While it's been tough lately thanks to the pandemic, here's what I presented at RailsConf 2018 about why I felt GraphQL was the future of APIs with Rails, and it's continued to pay off in the few years since:
One of my proudest moments of the last year was introducing Architecture Decision Records to my engineering organization as a way to deliberate on and make team-wide decisions. I noticed a pattern of senior engineers going off on their own tangents while more junior engineers didn't know how to participate in, or learn from, the discussion around technical choices that faced our team. After identifying around 10 of these decisions in-flight at a critical point this year, I proposed using log4brains: an open source tool to publish and catalog ADRs via Markdown that would allow our team to use our familiar GitHub Pull Request workflow to debate and decide on our technical choices. The reception for this tool has been great, and I've heard from all levels of engineers that they appreciate the dedicated space for these discussions and the new process.
Beyond starting RubyGems.org, I started a co-working space in Buffalo, was one of the first employees for a startup in Berlin, and I'm currently creating a food co-operative here outside of Boston. I'd be excited to help figure out how to launch a new version of the Reddit API and kick off its developer toolkit right.
To be transparent: I've been critical about Reddit publicly, especially as it has had outsized impact on Internet culture and the world at large the last few years. It's clear to me the folks at Reddit want it to be a force for good, and I'd be honored to be a small part of making that so.
I'd love to talk about next steps. My resume is here and I'd be happy to provide references if requested. Thanks for reading!