text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** And if you don't know how to give feedback, I'm pretty sure this is answered in the community guide on how to give constructive, positive feedback, right? |
**Stephen Augustus:** We have speaker guides, we have conference guides, we have a code of conduct for the conference... |
**Constance Caramanolis:** I've tweeted about it. We've tweeted about how to give constructive feedback, yeah. But you can actually also search "Constructive feedback", there's a lot of different ways to do it. There's a lot of training on it. |
**Gerhard Lazu:** So there's that as well. Okay. So be kind. This is something that keeps showing up, and maybe don't take things too seriously, right? People do make mistakes sometimes, and it's not meant to hurt you in any way, right? It just happens, so don't take it too seriously. If you didn't like it, don't be a ... |
**Constance Caramanolis:** Yeah. I think there's something to add to that, too... People will make mistakes, and sometimes you'll accidentally be a jerk. And it's not okay, but the thing to do is to own it. Apologize \[unintelligible 00:51:00.10\] Don't just ignore it, because then it's not actually addressing it, and ... |
**Stephen Augustus:** And I think there's a kind of aphorism that people agree and disagree with, which is "Assume good intent." And it's tricky, because when you walk into situations, there's of course a balance. I think that in the open source space you wanna be good, and kind, and true, and assume that people are op... |
\[52:22\] So I think that there is, for sure, a balance of having thoughtful discussions, and again, doing the work to be thoughtful in your communication to people. I guarantee you, anytime I see -- there are quite a few communities within the cloud-native space that I work on, across Kubernetes, across KubeCon, for t... |
**Gerhard Lazu:** I think everybody should do that. It shouldn't be just Stephen. It's all of us, right? It's the community that we build. |
**Constance Caramanolis:** We are responsible. |
**Gerhard Lazu:** We know it's hard - certain degrees of hard, but it's hard... But it's worth it. It's worth it to be kind, it's worth it to be nice; it's worth to actually invest in this... Because it is ours. KubeCon is all of ours, so what do we want it to be? Well, it happens to be my favorite conference out of al... |
**Stephen Augustus:** You're part of it. You're part of team CloudNative. I think that the second you decide that you want to attend, the second you stare at a GitHub repo, the second you join a mailing list for one of these projects, you're part of it. We do this for you, and we can't do this without you. So bring you... |
**Constance Caramanolis:** I also think too, KubeCon became so big because the community is great, and because we keep on reflecting on what our standards and our commitment is to the community, and trying to improve ourselves, and we don't stay stagnant. And that's why these conferences are so large, it's because we d... |
**Stephen Augustus:** So a PSA on that that I think is important to hear as we prepare for hopefully more people to start doing in-person things again - and I mention this because it's very important right this second, because I've seen it happen... These projects, these communities, these events are held by a code of ... |
**Gerhard Lazu:** Thank you, Stephen, thank you, Constance. This was like -- if you've made it to the end, you got all the good parts; and if you've made it this far, rewind ten minutes and listen again, because that was the best part of this interview; it's really powerful. We have to acknowledge the negative parts, b... |
**Constance Caramanolis:** You can't ignore it. |
**Stephen Augustus:** When you decide to ignore, that makes you culpable. |
**Gerhard Lazu:** \[56:01\] That's how it starts. |
**Constance Caramanolis:** Yeah. |
**Gerhard Lazu:** That's the beginning. Who knows what the end will be, but don't get there. Just catch it early. |
**Constance Caramanolis:** I know I've had horrible experiences in tech, and I will say, one thing that made me wanna keep on staying was this community. And if it's to ever resemble some of my previous bad experiences in tech, I would just be like "This isn't worth it for me." So I am very proud of this community for ... |
**Gerhard Lazu:** So first of all, you mentioned about tech and how abysmal things are in tech, Constance. And you're right. We all have different perspectives. The under-represented groups have it the worst, and most of you have no idea what it's like. It can get really bad. And I think I'm finally - after years and y... |
**Stephen Augustus:** There are limits, for sure. But I think that getting cert'ed in the cloud-native space, I definitely was very excited, bright-eyed, and bushy-tailed, and excited about learning the technology... I don't really care about the technology as much anymore. I spend a lot less time on the command line t... |
Because seeing us create a space where, like you said, people can thrive and learn and grow, and then how -- you know, with any good technology, especially in our space, it's like "How do we make it distributed? How do we scale it?" So it's beyond that, and this is a great example. I can't necessarily have this one-to-... |
**Gerhard Lazu:** This is too good. I had too much fun. I'm not sure whether it's safe to have this much fun on a Friday, but this made it the best part of the day for me, so thank you. |
**Stephen Augustus:** I sure hope so. \[unintelligible 00:59:52.23\] |
**Constance Caramanolis:** Yeah, this was great. Thank you! |
**Gerhard Lazu:** Thank you. This was the best conversation I had all week, so thank you. |
**Stephen Augustus:** Absolutely. \[laughs\] |
• The evolution of software deployment methods, from manual FTP and rsync to automated Git pushing. |
• The concept of Continuous Delivery and its acceleration around 2012/2013. |
• Dave Farley's personal experience and inspiration for writing the book "Continuous Delivery" with Jez Humble. |
• Formative experiences that shaped Farley's understanding of software development, including working on complex projects and adopting agile methodologies. |
• The importance of experimentation, learning from mistakes, and scientific rational thinking in software development. |
• Continuous delivery as an approach to facilitate efficient progress and engineering practices. |
• The impact of continuous delivery on teams and individuals, with Gerhard Lazu sharing his personal experience and gratitude. |
• The challenge of changing people's habits and adopting new ways of working |
• The importance of data-driven decision making in software development |
• The difficulty of establishing and maintaining a positive culture within an organization |
• The interplay between people and practices in driving the success of software development teams |
• The potential for technology to amplify the talents and skills of developers, rather than being a heroic exercise carried out by geniuses |
• The distinction between "software engineers" and "software developers", and the implications of this distinction |
• Martin's focus on simplicity and separation of concerns is emphasized as an essential aspect of his design approach |
• The importance of test-driven development (TDD) in enhancing the property of focusing on separation of concerns is discussed |
• Dave Farley's background and experience with continuous delivery, agile methods, and extreme programming are highlighted |
• The early 2000s technology stack used for continuous integration and delivery is described, including Java, CruiseControl, Ant files, and homegrown tooling |
• Examples of innovative and sophisticated tooling developed by LMAX team members, such as a test distributor and a dynamically managed compute grid, are mentioned |
• Performance demands and software development in the early 2000s |
• Challenges of building tools and systems without existing frameworks or platforms (e.g. no open source software, no GitHub, etc.) |
• Introduction of Agile principles and continuous delivery at ThoughtWorks |
• Development of BDD, continuous delivery, and mocking concepts |
• Legacy of earlier software development methods and the reaction to them that led to the Agile movement |
• Emergence of cloud-native systems and projects (e.g. Argo CD, Event Sourcing) |
• Evolution of CI/CD tools and systems over time (e.g. Jenkins, CircleCI, GitHub Actions) |
• Cloud computing has changed the focus from storage economics to compute costs |
• Normalizing data is no longer necessary due to cloud-based services and sharding |
• The cloud allows for easy access to spin up resources, but also raises the bar of abstraction |
• Continuous integration and delivery tooling needs improvement, particularly in terms of opinionated software that provides clear guidelines for deployment pipelines |
• Build systems like Gradle are examples of opinionated software that make development easier |
• A standardized pipeline concept is needed for CI/CD, similar to the Kubernetes API |
• There is a need for a next building block or standardization in CI/CD tooling to simplify pipeline declaration and execution |
• Minimum deployment pipeline requirements |
• Importance of fast feedback and confidence in software releasability |
• Key stages in a deployment pipeline (e.g. unit tests, acceptance tests) |
• Template for pipelines with parallelized and scalable architecture |
• Definition of a deployment pipeline as a process from commit to releasable outcome |
• Goal of continuous delivery is to have software always in a releasable state |
• Example of a deployment pipeline for an Erlang-based project |
• Critique of a deployment pipeline that automatically deploys to production within 15 minutes |
• Discussion of pipeline optimization and testing strategies |
• Explanation of the concept of instruction pipelining in computer processors and its relation to deployment pipelines |
• Criticism of conflating different types of tests in a deployment pipeline |
• Importance of evaluating deployability and configuration of systems, especially in high-stakes environments |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.