text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** Exactly. |
**Adam Stacoviak:** I'm just doing some math for you who don't know how time works. |
**Gerhard Lazu:** Thank you. Thank you, Adam. So that's one thing which I would like to look into more, because one thing which -- I mean, I had many great conversations in these ten episodes, but the one which really resonated with me was the one with Justin Searls about reliable software, trusting your software, opti... |
So in my mind, how do we make it more reliable? How do we fail less? How are more available? I think we have made some great improvements, but I don't think we're there yet. I don't think we'll ever be there, but at least we'll be improving. That's where my mind is at. |
**Adam Stacoviak:** Well, Kaizen, right? Come back to Kaizen. Speaking of Kaizen, behind the scenes we have a T-shirt design which is simply the Japanese characters that make up the word Kaizen, which I feel like is an adopted -- we rose this flag, Gerhard, so I feel like this is an adopted company-wide mantra, for me ... |
So we do have a shirt coming out soon, it's the Japanese characters that represent Kaizen. It's a super-cool shirt, it's on a super-soft T-shirt... You're gonna love it, and I'm excited to wear that to represent this idea of continuous improvement and embracing that. |
**Gerhard Lazu:** And on that high note, episode 20 is a wrap. Thank you, gents. It was a pleasure. Looking forward to the next one. |
**Adam Stacoviak:** Me too. |
**Jerod Santo:** Kaizen. |
**Adam Stacoviak:** Kaizen. |
**Gerhard Lazu:** Kaizen. |
• Kaizen: a concept of continuous self-improvement |
• Reflecting on improvements for the show's application and setup every 10 episodes |
• Importance of retroactive feedback loops in improving infrastructure |
• Past improvement process: sharing changes once per year, but now aiming to improve more frequently |
• Recent issues with Fastly CDN, including a global outage affecting multiple services (BBC, emojis, etc.) |
• Reviewing the impact of the outage on Changelog's performance and plans for future improvements |
• Discussion about Grafana and internet downtime |
• Incident where Fastly had an outage during the release of a popular episode of The Changelog |
• Importance of redundancy and double-monitoring systems (e.g. using Pingdom as backup) |
• Debate on whether to rely on Fastly for stats or have a redundant system |
• Exploring options for multi-cloud and service-level solutions |
• Gerhard's idea to use Cloudflare AND Fastly, decouple assets from local storage, and run multiple instances of Changelog across different services (e.g. Linode, Render, Fly) |
• Discussion on the costs and benefits of implementing redundancy |
• Discussion of using MaxMind or GeoIP database for geolocation data |
• Review of Cloudflare's analytics capabilities and potential benefits of multi-CDN setup |
• Long-term direction for the platform, potentially including multi-CDN and improved analytics |
• Immediate tasks to be done on the platform, including managing incidents and creating a plan for incident response |
• Current incident: deleted DNS token causing certificate issues, requiring immediate attention |
• Discussion of activity logs and importance for services with multiple users, with a need for more than 30 days of history |
• Incidents: Token deletion on June 19th was suspected to be an anomaly due to unusual time. |
• Investigation: Discussion on how to investigate and identify who deleted the token. |
• Incident Management: Exploring ways to improve incident management, including consensus-based deletion of access tokens. |
• DNSimple Configuration: Reviewing DNSimple configuration and considering using Kubernetes to manage tokens. |
• Monitoring and Alerts: Discussing the need for proactive monitoring and alerts to catch issues before they cause problems. |
• Incident management and its elements |
• Runbooks as a way to codify incident response steps |
• Importance of automation vs ROI for small teams |
• Use of incident management platforms such as FireHydrant and Incident.io |
• Creating runbooks retrospectively after incidents occur |
• Benefits of using incident management platforms to store and retrieve runbooks |
• Creating backup plans in case of catastrophic failures |
• The hosts discuss their testing process for backups and restoration |
• Importance of pursuing knowledge and sharing content over ensuring uptime at all costs |
• Exploring different platforms (Incident.io, FireHydrant, Render, Fly) for running Changelog and potential benefits/disadvantages |
• Discussing the importance of trying new things and innovating, even if some ideas may fail |
• Mention of setting up incident management and Fastly logging integration for improved visibility and monitoring |
• Difficulty in setting up Fastly logging due to lack of direct integration with Grafana Cloud |
• Discussion of integrating Honeycomb with Fastly and Grafana Cloud |
• Goal to visualize and reduce deployment time from git push to production |
• Analysis of current pipeline inefficiencies and potential for smartening it up |
• Cache invalidation problems associated with optimizing deployment processes |
• Mention of Charity Majors' "15 minutes or bust" goal for code deployment time |
• Reducing complexity in software development |
• Optimizing performance for slow tasks (15-minute delays) |
• Visualizing and understanding the steps involved in these tasks using Honeycomb |
• Migrating from local disk storage to a managed PostgreSQL database or alternative solutions like CockroachDB |
• Moving media assets to an S3 object store to improve restore times and scalability |
• Simplifying the app by making it stateless and leveraging cloud capabilities |
• Potential for unlocking new features with S3 and unmanaged database |
• Chaptering functionality in podcast episodes, including ID3v2 support and FFmpeg integration |
• Motivation to "bite off" chaptering feature as a win, along with stateless capability |
• Pre-processing chapters locally vs. relying on FFmpeg |
• Comparison of YouTube video segments and desired Changelog audio features |
• Client-side compatibility and benefits for indie podcast app developers |
• Automatic file upload and drag-and-drop functionality for blog posts |
• Discussion of pushing podcast boundaries |
• Importance of collaboration on improvement ideas |
• Proposing to implement improvements and revisit in 10 episodes |
• Reference to the concept of "kaizen" (continuous improvement) |
**Gerhard Lazu:** So I really wanted to talk to you about this topic of Kaizen. Kaizen, for those that's the first time they hear this, is the concept of the art of self-improvement specifically. And that is really powerful, because it's the best way that you have to improve yourself, and to always think about "How can... |
**Adam Stacoviak:** Kaizen. I love it. |
**Jerod Santo:** Always Be Improving. ABI. |
**Adam Stacoviak:** ABI, yeah. Always Be Something. ABS. |
**Gerhard Lazu:** I'm pretty sure that means something else for others, ABS, but yes... |
**Adam Stacoviak:** Automatic Breaking System, that's what it refers to for me... |
**Gerhard Lazu:** \[03:59\] The reason why I care so much about this is that having been part of Pivotal, this company which isn't anymore - it was acquired by VMware last year or two years ago - is that one of the core principles was to always be improving. "Be kind" was there as well. But always be improving was some... |
So having done it for 5, 6, 7 years, it's so deep-ingrained in me I cannot not do it. It's part of me. And I do it continuously. And I think the infrastructure setup that we've been rolling for some number of years has been an embodiment of that. Every year it has been improving. It was rooted in this principle. |
Now, one thing that we did in the past differently is that we improved, or at least we shared those improvements once per year. It was a yearly thing. And one of the ideas for the show was to do it more often, to improve more often. So we can improve in smaller steps, but also figure things out a lot, lot quicker, what... |
**Adam Stacoviak:** It works out at about every two-ish months essentially we get a response, a blip, a feedback loop, whereas before it was like once, or more recently twice in a year; if it's Kaizen every ten shows, then we get around four or five(ish) per year if you're shooting for 52 as a year. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.