text stringlengths 0 1.8k |
|---|
[3422.34 --> 3427.32] And when you operate with multiple systems in parallel, which is what's happening in the |
[3427.32 --> 3430.64] real life of not small organization or large organizations. |
[3430.64 --> 3436.22] I'm looking forward to it that foundations and various working groups start working on |
[3436.22 --> 3440.96] specific standards for open telemetry so that they actually standardize the events. |
[3441.14 --> 3443.52] Because right now it's still an open question. |
[3444.00 --> 3450.06] So it's a very idealistic view that every CI system exposes the same events, the same metrics |
[3450.06 --> 3450.94] and the same logs. |
[3451.10 --> 3452.48] It's not a case yet. |
[3453.02 --> 3455.32] And there is a lot of standardization work to happen. |
[3455.86 --> 3460.42] I see such work, for example, happening in the Continuous Delivery Foundation for CD events. |
[3460.42 --> 3464.32] But for open telemetry, I would like to see that as well. |
[3464.52 --> 3465.06] That's a good point. |
[3465.16 --> 3465.60] Yeah, you're right. |
[3465.80 --> 3466.88] It's still very early days. |
[3466.94 --> 3471.42] As you mentioned, this whole new ecosystem is still very young, right? |
[3471.46 --> 3474.18] It only just started maybe a year ago, two years ago. |
[3474.34 --> 3475.48] It's very recent anyways. |
[3475.72 --> 3478.78] Yeah, it's just a sandbox project in ICNCF these days. |
[3479.16 --> 3484.56] But I hope that it will become incubating very soon because the adoption for open telemetry |
[3484.56 --> 3485.66] is already massive. |
[3486.00 --> 3488.52] And there are so many players on this space. |
[3488.52 --> 3492.88] So from my point of view, it's totally justified that it's transferred to incubating. |
[3493.12 --> 3496.36] Is there anything coming in the next six months that you want to share with us, Cyril? |
[3496.58 --> 3502.54] We have just donated the open telemetry Maven integration to the open telemetry community. |
[3503.08 --> 3505.48] So it's moving fast and we get feedback. |
[3505.64 --> 3507.00] So we are progressing fast here. |
[3507.06 --> 3507.58] It's great. |
[3508.22 --> 3510.48] The open telemetry Ansible integration. |
[3510.48 --> 3515.52] We have donated the Ansible integration to the Ansible community itself. |
[3516.20 --> 3522.42] We are iterating at the moment and we are rolling it out inside Elastic to really battle |
[3522.42 --> 3523.06] test this. |
[3523.26 --> 3524.94] So it's moving as well. |
[3525.04 --> 3530.18] So these are great milestones for us to expand the ecosystem of tools that we integrate. |
[3530.36 --> 3531.32] Oleg, what about you? |
[3531.44 --> 3533.60] It's kind of public and changing jobs. |
[3533.82 --> 3538.44] I still cannot announce what's the next one, but I'm sure it will be quite interesting. |
[3538.44 --> 3540.00] It's around open source. |
[3540.42 --> 3542.62] It's around observability as well. |
[3543.44 --> 3547.86] I will definitely keep working with Cyril and many other contributors in this area. |
[3548.12 --> 3549.04] Looking forward to that. |
[3549.56 --> 3551.04] We will keep working on Jenkins. |
[3551.42 --> 3557.60] I will be publishing my vision for Jenkins and some bits of the roadmap in the coming weeks. |
[3558.22 --> 3562.10] So that if you're interested to see Jenkins evolution, the community is strong. |
[3562.26 --> 3564.92] There is a lot of different developments happening in there. |
[3564.92 --> 3570.32] Yeah, I'm looking forward to seeing what we ship to the users in just a few months, maybe |
[3570.32 --> 3570.62] years. |
[3570.80 --> 3572.30] Well, this has been a great discussion. |
[3572.64 --> 3573.24] Thank you very much. |
[3573.28 --> 3575.88] There's so many things they need to go and check up on now. |
[3575.98 --> 3577.42] All very exciting things. |
[3577.72 --> 3582.08] And I look forward to what happens in six months in this space because it's really, really |
[3582.08 --> 3582.42] interesting. |
[3582.56 --> 3584.12] It just ties so many things together. |
[3584.26 --> 3584.88] I'm very excited. |
[3585.32 --> 3586.22] Thank you very much for today. |
[3586.22 --> 3586.96] Thank you very much. |
[3587.08 --> 3587.30] Thank you. |
[3587.30 --> 3593.40] Thank you for tuning in to another episode of Ship It. |
[3593.76 --> 3595.60] I enjoyed making it for you. |
[3595.82 --> 3598.94] This is just one of the podcasts for developers that we ship. |
[3599.30 --> 3602.76] Go to changelog.com forward slash master for the rest. |
[3603.32 --> 3609.32] You can join me and the rest of our community at changelog.com forward slash community. |
[3609.92 --> 3611.50] There are no imposters in our stack. |
[3611.86 --> 3613.10] Everyone is welcome. |
[3613.10 --> 3618.24] Huge thanks to our partners Fastly, LaunchDarkly and Linode. |
[3618.86 --> 3622.18] Thank you Breakmaster Cylinder for all our awesome beats. |
[3622.70 --> 3623.80] That's it for this week. |
[3624.12 --> 3624.82] See you next week. |
[3643.10 --> 3653.00] Game on. |
• Slinging code vs getting it right: the difference between shipping quickly and doing it correctly |
• The importance of psychological safety, autonomy, and alignment in software development teams |
• Velocity vs fluidity: optimizing for speed or smoothness in delivery processes |
• Consistency over time: maintaining a healthy pace across years rather than just short-term goals |
• Knowing where to point teams: the importance of shared understanding and business value in successful projects |
• Disconnect between developers and product owners leads to a lack of understanding of "why" and ultimately facilitates negative externalities |
• Building software for business value or customer outcomes requires understanding the equivalent "why" and correlating points to business value |
• Complexity in technical solutions makes it difficult to answer the question of "why" |
• Detachment from the "why" can lead to a lack of excitement, creativity, and innovation among developers |
• A sustainable and healthy development pace is one that allows for asynchronous chewing and deliberate pacing, allowing for forward progress and hope despite blockers and complexity. |
• The importance of understanding human productivity and creativity as influenced by brain function and social interaction |
• Justin Searls' Twitter poll on whether DevOps has sped up or slowed down teams' ability to deliver software, with 44.5% voting "Sped up" |
• Critique of the term "DevOps" for becoming a buzzword that overemphasized automation and neglected core desires such as ease of use and minimal complexity |
• Justin's experience with Heroku as a prime example of what he wants in terms of simplicity and ease of deployment, but notes that this is not the market trend |
• Discussion on how DevOps has led to teams hiring "DevOps people" to manage cloud computing, rather than simplifying operations |
• Shared understanding of "DevOps" being a point of contention among respondents, with Justin arguing that typical DevOps activities do not truly automate problems |
• Git push as the foundation for a resilient system |
• Critique of overemphasis on new technologies and ignoring fundamental principles in DevOps |
• Parallels between test-driven development and infrastructure/DevOps |
• Importance of total cost of ownership and return on investment when considering testing and automation |
• Criticism of generic, context-free advice on testing and DevOps tools |
• Need for operational knowledge and understanding of how systems integrate and fail |
• Value of automation in detecting and notifying issues, but not replacing human expertise |
• The burden of knowledge and experience required for complex systems and infrastructure |
• Transitioning from commodity services to self-managed infrastructure and the difficulties involved |
• Recognizing inflection points where teams must adapt and learn new skills, such as testing and DevOps |
• The importance of building in confidence and consistency through testing and automated pipelines |
• Strategies for addressing flaky tests and achieving consistent builds |
• Understanding the nuances of scaling systems and making informed decisions about infrastructure choices |
• The importance of distinguishing between actual system failures and flaky implementation problems in test results |
• Limiting the scope of integration tests due to complexity and resource constraints |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.