text stringlengths 0 1.8k |
|---|
• Solutions for technical issues with GitHub Codespaces and Elixir/Postgres installation |
• Using a temporary solution with an old machine until a new MacBook is available |
• Update on moving uploads to cloud storage (S3) and deprioritizing tasks due to other commitments |
• Investigating a mysterious bug in an Elixir/Phoenix application involving character encoding and URLs |
• Discussing how to handle bugs in dependencies and the importance of staying up-to-date with the latest versions |
• Describing the process of upgrading Phoenix from 1.5 to 1.6, including encountering API changes and breaking tests |
• Refactoring a meta module after discovering that the upgrade broke metadata on all pages |
• The concept of "yak shaving" and how it relates to solving problems and taking shortcuts |
• The concept of a "yak shave" is discussed, referring to the phenomenon where upgrading or improving one aspect of a system leads to additional work and complexity |
• The idea that sometimes it's necessary to "bite off more than you can chew" in order to make progress |
• A discussion about being in a state of flow and how it can lead to significant productivity gains, even if the initial goal is not achieved |
• Mention of several upcoming gifts or topics for future episodes, including: |
• Using Crossplane to manage Kubernetes infrastructure |
• Integrating with Honeycomb |
• Exploring Dagger |
• Parka |
• Reflection on the evolution of the podcast's infrastructure and network over time |
• The hosts discuss the importance of trying out various tools and sharing their experiences on the show |
• Feedback from the podcast is shared with vendors, including Honeycomb and Crossplane |
• The hosts emphasize the value of collaboration and giving feedback to improve tools and services |
• The Ship It initiative is mentioned as a way for end-users to provide feedback to vendors |
• Partnerships are discussed, with many companies being thanked for their support |
• The hosts reflect on the show's journey and thank listeners for their participation |
• Gerhard shares an extreme example of a yak shave, where he spent three weeks troubleshooting internet connection issues with multiple routers and internet connections. |
• The group's initial attempts to discuss the issue are interrupted by laughter, but eventually they manage to compose themselves and explore the logistics and humor in Gerhard's situation. |
• The conversation devolves into jokes about over-engineering and redundancy, with the group suggesting that Gerhard's experience is an extreme example of a principle often referenced in sci-fi (e.g. "why build one when you can build two?"). |
• The episode ends with a lighthearted tone, poking fun at Gerhard's dedication to solving his internet issues. |
• The idea of redundancy and over-engineering becomes a recurring theme, with the group joking about Gerhard's need for multiple ISPs and routers. |
**Gerhard Lazu:** So we're back for the third Kaizen. I can't believe it's been 30 episodes, and I'm not the only one. Adam can't believe either than it has been 30 episodes of Ship It. |
**Adam Stacoviak:** Yeah... It really is insane, honestly... I mean, this show was just an idea recently. I think anybody who makes things come to life from nothing is always flabbergasted by the creation, I suppose, once you sort of get into it... But podcasting is a little bit different, because it really is a journe... |
**Gerhard Lazu:** Yeah. I mean, we shipped it, right? It took us a while; it took us five months to ship the first three episodes... And then it was like a roll. What blows my mind is that my mind is on episode 40. And most people don't realize this. The next five episodes are pretty much locked in. The guests, the top... |
**Jerod Santo:** Yeah, you just live in the future. I think you might be the most prepared and scheduled out podcaster in the entire universe, Gerhard. |
**Gerhard Lazu:** \[laughs\] Okay... I want to think that's a compliment... |
**Jerod Santo:** I'm happy that I got us scheduled out through December, but you're -- no, it is. |
**Gerhard Lazu:** Thank you. |
**Adam Stacoviak:** That's a compliment. |
**Gerhard Lazu:** I don't want to leave myself open to unique encounters and like... |
**Jerod Santo:** \[04:15\] Yeah, that's a challenge. Serendipity is taken out when you're scheduled out. |
**Gerhard Lazu:** That is a great word. I haven't heard it in a while. I thought I was the only one using it. Okay... |
**Jerod Santo:** Happy to surprise and delight. |
**Gerhard Lazu:** Right. Well, thank you very much in which case, Jerod. I appreciate that. Thank you. And what I'm really excited about is -- I don't think many people realize this, but there's like a theme to this; there are like multiple themes. A couple of episodes, they kind of cluster together, and there's a buil... |
**Adam Stacoviak:** Yeah. |
**Gerhard Lazu:** And there was something which I wanted to understand, which I didn't at the time... Was why was an unhealthy pod put back into service. Do you remember that? |
**Jerod Santo:** I do remember that. We didn't have answers. |
**Gerhard Lazu:** Yes. So my answer is we're using the "latest" tag. What that means is that if something is unhealthy, and it has to go back to the previous one, it will use the "latest" tag. But "latest" has moved on. So it doesn't keep the old SHA, the one that was working; it says "always the latest." So if you wer... |
**Jerod Santo:** Oh, you're pointing back to the same version, which is broken. |
**Gerhard Lazu:** Exactly. Exactly. |
**Jerod Santo:** Why are we doing that? |
**Gerhard Lazu:** Um, some corners have been cut... \[laughter\] |
**Adam Stacoviak:** The honesty, I love it. |
**Gerhard Lazu:** ...and that worked well for quite some time. So I have to say that even though those corners have been cut, there was like a trade-off to be made. It was like a conscious trade-off... And it only failed once. So that trade-off has bit us once. |
**Jerod Santo:** Right. |
**Gerhard Lazu:** But I think it is high time that we revisit the whole GitOps approach. The GitOps approach that we have, but not really have, to how we run our infrastructure. So while we do version all the manifests, and everything is in the repo, and we apply them, some manifests reference "latest", and "latest" ca... |
The thinking goes we always want to be running "latest". When do you not want to run "latest"? Apparently, when "latest" is broken. |
**Jerod Santo:** \[laughs\] Exactly. The one time when you definitely do not. |
**Gerhard Lazu:** That's when you don't want to run "latest". \[laughs\] But that's something that -- yeah, we will be investing in. I will be spending a bit of time on that, among many other things. But that explains this incident too, which - I didn't have an explanation ten episodes ago. |
**Jerod Santo:** Yeah. How did you learn of this? |
**Gerhard Lazu:** Um, I looked at the manifest, and I tried to understand what happens. So I went through the steps of what would happen, or of what happens in Kubernetes when -- like, the new one gets put in service, it fails, the old one crashes, and when it gets restored, it gets restored with "latest". So that's wh... |
**Jerod Santo:** \[07:56\] So my developer brain sees something like this, and I think infinite loop. Is that going on here, or does it just fail? Because if it runs "latest", "latest" is broken, it runs "latest", "latest" is broken... Does it just keep doing that over and over again? |
**Gerhard Lazu:** Yeah. So in our case, what happened was that the version that was running - that crashed. Because it's just meant to restore it, right? It crashes - not a problem, it will come back. |
**Jerod Santo:** Right. |
**Gerhard Lazu:** But when it comes back, it doesn't know which version it should come back with, because it has "latest", and it resolves that when it boots. And "latest" has moved along, which is where the problem comes from. So we need to capture the version of the app that we want to run. Not the app, it's the app ... |
**Adam Stacoviak:** That's a challenge. |
**Jerod Santo:** It's always nice to get answers to mysteries... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.