text stringlengths 0 2.29k |
|---|
• The importance of knowing when to pause or quit projects |
• Experimentation with video content and GitHub discussions |
• Changes in the podcast's schedule and future plans |
• Keeping up with the hosts' online presence (Twitter, Changelog Slack, etc.) |
• Exploring ways for listeners to stay connected with the hosts |
• Regressing to the original podcast format and schedule |
• Pausing continuous podcast delivery to focus on improving infrastructure and developing partnerships |
• Improving CI/CD workflows with Dagger, a code-based pipeline management system |
• Migrating from Circle CI to GitHub Actions using Dagger |
• Releasing SDKs for writing CI/CD systems in code (Python, Go, Node.js) |
• Eliminating YAML, CUE, and makefiles in favor of Go code and mage files |
• Dagger v0.1 released, replacing old pipeline |
• Introduction of namespace runtime "image" |
• Building and publishing Changelog runtime image to GitHub Container Registry (GHCR) using Dagger v0.3 |
• New features for building and publishing images with various dependencies (e.g. Elixir, Node.js) |
• Automated caching and reusing of dependencies to speed up build process |
• Ability to easily update dependencies by changing a single string in code |
• Pipeline will automatically update dependent files (e.g. README) when dependency is bumped |
• The host company's codebase can be run on GitHub Codespaces using a devcontainer.json file |
• Chris made a pull request allowing the codebase to be run on Codespaces, and Gerhard followed up with another PR that references an already built runtime image from GHCR for faster performance |
• Dagger is being used to redefine CI/CD as code, making it possible to orchestrate containers in code rather than using scripting or YAML |
• The company is one of the first to use Dagger's services support feature, which allows spinning up a PostgreSQL container for tests inside the Dagger engine |
• The company deploys every push to master as a release and runs tests on pull requests |
• Implementing GitHub Actions to run tests for every pull request |
• Leveraging Docker engine for CI/CD tasks, including building and running longer-running environments for deployment previews |
• Exploring Dagger services support for longer-running processes in CI/CD |
• Rotating secrets and integrating 1Password as a team |
• Addressing the LastPass leak and migrating to 1Password |
• Key rotation and updating API keys for various integrations (Slack, Campaign Monitor, etc.) |
• Discussing improvements to infrastructure documentation and diagrams |
• Replacing Algolia with Typesense as search index |
• Exploring alternative caching solutions due to performance issues with Erlang caching system |
• Using Postgres as a cache for pre-computed feeds and serving them as static content |
• Integrating Phoenix with Honeycomb for observability and metrics |
• Planning to test the new caching solution in production |
• Discussion of using feature flags for testing a new implementation |
• Proposals to test the new implementation on a limited set of users (50/50 split) |
• Alternatives to feature flags (simple if statement with random selection) |
• Observability and logging issues, including a recent change that caused log files to stop logging |
• Explanation of how telemetry plug disables logging in production |
• Discussion of using Honeycomb for observability |
• OpenTelemetry plug-in integration |
• Review and merging process discussion |
• Changelog experiment production results: serving live feeds from Postgres cache |
• Enabling multiple instances of Changelog and global distribution |
• Serving different feeds to different requesters (e.g. Spotify) |
• Precomputed text storage limitations in Postgres |
• Fly's role in reducing reliance on CDN and enabling distributed apps |
• Technical difficulties with understanding and troubleshooting cache issues |
• Using Fastly to create a dynamic app close to users, but complexities and challenges |
• Embodiment of the Fly vision and overcoming cache limitations |
• Cache experiment results and implications on app performance |
• Discussion on caching on write vs. read and potential solutions |
• PostgreSQL as a service (e.g., Crunchy Data or Supabase) for scalability and management |
• Trade-offs between managed databases and self-hosted options |
• Plans for the next Kaizen episode and publication on the Changelog feed |
• Discussion of a business plan to turn Postgres into dollars |
• Efforts to use 1Password secrets programmatically in CI systems without running the Connect server |
• Consideration of migration from 1Password or using an alternative secret management solution |
• Review of passwordless systems, including 1Password's "Pass keys" feature |
• Adam Stacoviak teases Jerod Santo about singing a song poorly on a previous episode |
• Gerhard Lazu announces he will take time off from recording Ship It episodes and go to Dan-Tan instead |
• The group discusses and jokes about the idea of going to Dan-Tan every week |
• They discuss future plans for the podcast, with an upcoming episode in 2.5 months |
**Gerhard Lazu:** Change is constant, and the one thing, the one lesson which really helped me was to not fight it, but embrace it. Some may think, "Oh, this sounds very agile-ish, and I thought we are post agile", but this is one constant, right? Change will always happen. And if anyone has been paying attention to th... |
**Adam Stacoviak:** That's a gut punch... |
**Gerhard Lazu:** Is a little bit... \[laughter\] But that's why I want to make it sound as positive as it can be, because it is. So if you remember when we started, I was experimenting so much, and trying so many things, crazy ideas, like "Let's use Kubernetes for Changelog." Remember that one? |
**Jerod Santo:** I do recall. I do. |
**Adam Stacoviak:** For sure. |
**Gerhard Lazu:** And then Jerod came and said "No, let's use Fly", and we tried that as well. So we were experimenting quite a lot before Ship It, or I was experimenting quite a lot before Ship It. And then, Ship It was taking more and more of my time, to the point that I was rushing from one thing to another thing, t... |
**Jerod Santo:** More experimenting, less shipping of Ship It. |
**Gerhard Lazu:** Less shipping off Ship It episodes, yes. That's right. But definitely shipping. So things will still continue changing on the Changelog side; the improvements will not stop. And if anything, a couple of other areas are already picking up, like Dagger, for example, for me, which means I need more of my... |
**Jerod Santo:** Embracing the change. So the big Why, if we say why in general, it's because you were stretched too thin in order to do the experimentations that you love, and you need some headspace. Dagger taking off, taking over, and Ship It being very much your passion project, a side project for you... had some f... |
**Gerhard Lazu:** That's right. I was checking myself, basically... And it's really important to know when to stop and what to stop. And to know how to rearrange things. And everything is temporary. I think that's something that is worth emphasizing. Nothing will last forever, not even us. |
**Jerod Santo:** Right. |
**Gerhard Lazu:** But hopefully, we've had some great time together. More amazing things will come, because this is not the end of it. It's just a pause, and we don't know how it will continue, in what shape or form... I don't think that's the approach - nothing wrong with the approach. But we can improve on it some mo... |
I remember episode 33, Merry Shipmas; recorded with the Upbound folks, recorded with the Dagger folks at the time, because I wasn't part of Dagger back then... And the third thing was Parca. We were profiling our app, and everything was running in Kubernetes at the time, to understand where the CPU time is spent. And P... |
**Jerod Santo:** So this is episode 90. So you made it to 90 episodes before this hiatus, this pause, so congrats on 90 episodes. Most podcasts do not make it that far even. Unfortunately not 100, which would have been a coup de gras; it would have been perfect. |
**Gerhard Lazu:** However, if it would have been 100, it would have felt more like the end. And this is not the end, right? So 90. Like, who stops at 90? Obviously, something else is going to come after 90. It's not a natural place to stop. 100 would be like "That's it. The book is done." |
**Jerod Santo:** Right. We would call it a grand finale, and you would sail off into the sunset. Well, for me, I am a little -- of course, embrace the change. I'm a little bit sad. I know we have a lot of listeners who truly love this show. It's a unique show in our catalog, in Changelog's catalog. You talk about thing... |
**Gerhard Lazu:** \[06:28\] Not a joke. \[laughs\] |
**Jerod Santo:** No, I do like it. I'm starting to like it. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.