Page 211 of 506 · Back to latest writing
Brendan Gregg, the performance engineer behind Flame Graphs and the USE method, builds tools for tracing software bottlenecks and measuring latency. His evidence-first approach shows developers how to locate system limits and debug infrastructure methodically.
Hillel Wayne, a software consultant and author, translates formal methods such as TLA+ for working programmers. His Crossover Project examines engineering’s real messiness, while his broader work asks teams to treat correctness as an explicit design choice.
Jessie Frazelle, a software engineer who built core Docker and Kubernetes components, approaches systems engineering and the technology industry from first principles. Her work across containers and hardware design brings blunt scrutiny to inherited technical assumptions.
Kellan Elliott-McCrea, formerly an engineering leader at Etsy, Dropbox, and Flickr, helped normalize continuous deployment and blameless post-mortems. His writing examines managing up, technical debt, and the trust required to build healthy engineering cultures.
Lara Hogan, a leadership coach and former engineering executive, clarifies the human side of software development. Her BICEPS and Manager Voltron frameworks offer practical ways to distribute support, resolve team friction, give clear feedback, and strengthen management habits.
Martin Kleppmann, a Cambridge researcher and author of Designing Data-Intensive Applications, untangles distributed systems, databases, and formal verification. His work pairs technical rigor with engineering ethics and a case for local-first software that frees user data from centralized clouds.
Werner Vogels, Amazon’s Chief Technology Officer, helped drive the company’s move into cloud computing and define its approach to distributed systems at scale. His frameworks reveal how software architecture and engineering-team structure reinforce one another.
Sandi Metz, a software engineer and author, champions simple, changeable object-oriented code over clever abstraction. Her practical guidance on testing and refactoring centers a durable judgment call: when duplication is tolerable and when design should evolve.