James Turnbull


If I had my hand full of truth, I would take good care how I opened it

Hiring Engineering Managers Part II

In Part I of this series, I talk about shaping the role and how to think about who to hire. In Part II, we’ll cover how to hire and what to ask to ensure you make the best possible hire. Competencies In Part I we discussed what an EM role is shaped like and what competencies we expect candidates to have. These cover both leadership and technical skills. Our final list looked like this:

Hiring Engineering Managers Part I

I do a lot of hiring, internally and as an advisor and consultant. I also read a lot about recruiting, and OMG, there are so many opinions about how to hire engineers. Everything from the interview process to take-home tests to the validity of whiteboard coding exercises has been explored and litigated. Some of my work also focuses on hiring engineering leaders for existing teams or the first engineering leader hired for an organization.

Aliases I have known

I have a lot of Bash/Zsh/Fish shell aliases. I’ve carted around a collection of dot files across laptops running both Linux and macOS and for use on systems I’ve managed. I’ve shared some of these, specifically for Docker, in the past. I wanted to do a post detailing some of the other aliases I have in case they are helpful to folks and talk through how to create and manage your aliases.

Investment decisions when building developer communities

tl;dr: In choosing where to spend your developer experience and advocacy dollars, investment in content, documentation, and initial developer experience is the most critical because it has the broadest addressable audience. But you also need to make an investment in more active engagements (Discord, Slack, Github, contributor resources) if you want to ensure involvement in your community is substantive and sticky. Building channels for developers and growing a developer community should take a tiered approach.

Sonic the search engine

For reasons that should be abundantly clear, I’ve been poking at alternatives to Elasticsearch. I’m living in a mostly Rust-based ecosystem right now working on Vector, so I started looking within that world. I found Sonic and decided to give it a whirl. Sonic is a “fast, lightweight, and schema-less search backend.” It’s written in Rust, licensed under MPL 2.0. It’s maintained by Valerian Saliou, who is one of the founders of Crisp.