A lot of folks want a map to Staff Engineer, and just as many Staff Engineers want to better understand their role. Towards that end, I'm working on a small project to collect folks' stories of reaching and operating as staff-plus engineers
Although we try to spend most of our time heads down building and learning, this is a good milestone for @ImprintPayments: we’re shipping ~4x faster, incidents down ~80%, and it’s working. We’re also still very, very early on the path.
wrote up notes on how @ImprintPayments is adopting a self-reinforcing loop to improve correctness, anchoring on the verification pattern that @poteto has popularized. Curious what other folks are doing / what folks have found next step to be!
What’s changed in “the unwritten rules” of engineering management since the 2010s, why are hands-on managers “back”, and what has it done to the engineer-to-CTO career path? With Will Larson (@Lethain). Timestamps:
00:00 Intro
08:20 Stories from Yahoo!
12:47 Digg’s v4 rewrite:
I'm hiring several key, hands-on engineering managers at @ImprintPayments. We'll work closely together. We'll build a product that a surprisingly large number of folks use as their top-of-wallet credit card. We'll use agents to rethink how software teams work. ✉️will@<handle>.com