Black Lives Matter.

May 30, 2020. Filed under stories 9

Last Wednesday evening I was (virtually) at an event that started with a silent moment in the memory of George Floyd. I wasn’t expecting it but appreciated the moment before it moved on to other topics. That moment came back to me the next morning, and threw into sharp contrast the extent that George Floyd’s death simply didn’t exist within the communities where I spend the majority of my time.

To lead, you have to follow.

May 25, 2020. Filed under management 128

Years ago, the company I was working with hired a new Director of Engineering, and the CTO was talking about why the new Director was an amazing hire. The new Director’s clinching accomplishment? The best ever explanation of the distinction between leadership and management. This turned out not to be a particularly effective way to evaluate hires, but it is an interesting topic.

The rush to "show value."

May 5, 2020. Filed under management 128

Some years back I had the strangest meeting in my career. Andrew (not real name) was my new manager, it was his first day on the job, and we were having the standard “get to know you” one-on-one meeting. My outgoing manager and I had been heavily involved in assessing and hiring Andrew, his interview performance was excellent, and I was legitimately excited to work together. So I was surprised when Andrew sat down, cradled his head in his hands, and lamented how much he regretted taking the job, how inept _his_ new manager was, and how terrible our engineering team was relative to his previous experience. What?!

April updates for StaffEng.

April 23, 2020. Filed under staff-eng 10

On March 19th, I posted "How do folks reach Staff Engineer?", and began posting stories of folks reaching and operating at the Staff Engineer level every Tuesday and Thursday.

Picking problems for programming interviews.

April 19, 2020. Filed under python 59staff-plus 26interviewing 4

Someone recently send me a note asking about whether their internal process for interviewing Staff engineers was a good one. They were particularly concerned that they were encountering a number of Staff-plus engineers who were struggling to write code for finding palindromes or reversing an array.

Minding our stories.

April 16, 2020. Filed under stories 9tech 1

If you took a minute to think back and pick your favorite conference talk, I have no idea what it was about, but I bet the talk was designed to tell a story. Likewise, I bet your favorite book, even if it’s non-fiction, is lanced through by a crisp, continuous narrative. If you wanted to explain your best or worst job, I bet you’d start by telling a story that captures the experience.

Testing Python projects for Google Cloud Run.

April 11, 2020. Filed under python 59gcp 4

I've been using GCP's Cloud Run for a handful of projects recently, including staffeng.com, and have generally been really pleased with it. Now that I'm familiar with it, I can get all of this working for a new Python project in about twenty minutes...

Staff engineer archetypes.

April 9, 2020. Filed under management 128staff-plus 26

Most career ladders define a single, uniform set of expectations for Staff Engineers. These career ladders attempt to identify the commonalities across many folks performing similar roles in their organization, but in the end these ladders are a tool that apply better against populations than people. In the case of Staff-plus engineers, career ladders paper over a number of distinct roles clustered under a single moniker.

Poking around Contentful.

April 5, 2020. Filed under contentful 1

Slightly related to my notes on build versus buy decisions, I spent some time specifically getting a feel for Contentful over the weekend and have written up some notes here.

Build versus buy.

April 5, 2020. Filed under management 128

A few years ago I was working on a contract negotiation with Splunk, and we kept running into what felt like a pretty unreasonable pricing structure. They wanted some number of millions of dollars for a three year license, which felt like a high price to pay for roughly thirty-two ascii characters in a particular sequence. Beyond the license, we'd still be responsible for operating the software and paying for the capacity to run it.