Code Story episode
S3 E18: Defining Modern Observability: How Honeycomb Redefined Systems Engineering with Charity Majors
Nov 17, 2020 · Season 3 · Episode 18 · 33 min
Observability for your Backend - Not Monitoring
Charity Majors didn't touch a computer until she was in college. In fact, she was raised in a religious, fundamentalist compound in rural Idaho, homeschooled and cultivating all of her own food. She went to college to study classical performance in piano. And though she loved piano, she decided to switch keyboards, so to speak, and pursue something in computers.
Been in San Francisco since she was 19, and never wants to leave. Outside of tech, she does some hand lettering as a hobby, reads a lot - and considers serial television as the highest modern art form. She is firmly motivated by using code to get stuff done - IE she doesn't do tech for fun. And in her words, she's made a niche out of being an infrastructure engineer.
Several years ago, she was the first infrastructure hire at Parse. While supporting the mobile backend as a service before and after the Facebook acquisition, she had access toa tool where she could slice and dice her infrastructure, to gain visibility into a particular section of services and answer questions. When she left - she realized that a tool of that nature was paramount to doing her job well. So she set out to build it again, and figure out how to coin the term observability.
This is the creation story of Honeycomb.io.
Sponsors
Free Lunch Coffee - discount coupon CODESTORY
Links
https://www.honeycomb.io/https://www.linkedin.com/in/charity-majors/https://parseplatform.org/
Leave us a review on Apple Podcasts
Amazing tools we use:
If you want the best publishing platform for your podcast, with amazing support & people - use Transistor.fmWant to record your remote interviews with class? Then, you need to use Squadcast.Code Story uses the 1-click product ClipGain, sign up now to get 3hrs of podcast processing time FREE
Credits: Code Story is hosted and produced by Noah Labhart. Be sure to subscribe on Apple Podcasts, Spotify, Pocket Casts, Google Play, Breaker, Youtube, or the podcasting app of your choice.
More episodes
Keep listening
Topics
Explore related conversations
Startup engineering team structure that actually ships
How to structure a startup engineering team: the models that work at 5, 15 and 40 engineers, how to split teams, and the org mistakes that quietly slow delivery.
How to choose a tech stack for a startup
A decision framework for choosing a startup tech stack: what actually matters, which choices are reversible, and how to avoid the rewrite that eats your Series A.
Build vs buy: a decision framework for technical leaders
When to build software in-house and when to buy it: a build vs buy framework covering total cost of ownership, differentiation, switching costs and vendor risk.