InfoQ Homepage Patterns of DevOps Culture Content on InfoQ
News
RSS Feed-
Puppet Releases Its 2020 State of DevOps Report
The State of DevOps Report 2020 released by Puppet reveals that internal platforms for self-service and effective change management practices were key for organizations to move up the DevOps evolution ladder. Security integration in the software delivery pipeline also plays a key role.
-
How Spotify Is Driving Data-Driven Decisions
Spotify’s infrastructure team has shared how by prioritising data, they’ve built an automated data collection platform that enables data-driven decision-making in DevOps and has improved their developer productivity and product value.
-
Security as a Product - a Coordination Game between DevOps and InfoSec
Kelly Shortridge, a product and strategy expert in information security, has described how security should be treated as a product. Analyzing the "we mindset" and game theory she puts forth DevOps and InfoSec as a coordination game.
-
Autonomy and Accountability: Randy Shoup’s Advice for Moving Fast at Scale
Randy Shoup, VP of engineering at WeWork, presented "Moving Fast at Scale" at CraftCon 2019, and discussed how he has organized teams for speed at scale without sacrificing innovation, business value, quality or team autonomy.
-
DOES London: RBS' Jennifer Wood on Conquering the Abyss and Rebirth
Jennifer Wood’s talk, ‘Our Heroes’ Journey to Agility’, opened the proceedings at this year’s DevOps Enterprise Summit in London. Wood first spoke at the conference last year, with her ‘The Art of Scaling Agile and DevOps’ and took the opportunity to build on the journey she is witnessing at RBS in her role as chief operating officer.
-
Fitness Functions to Ensure Architectural Goals Are Met
With fitness-function-driven development, we can write tests that measure a system’s alignment with architectural goals, similar to how we use test-driven development (TDD) to verify that features conform to desired business outcomes, Paula Paul and Rosemary Wang write in a blog post, describing the basic ideas of fitness functions and how architecture qualities can be verified.
-
The Evolution of Full Cycle Developers at Netflix: Greg Burrell at QCon SF
At QCon San Francisco, Greg Burrell talked about the journey towards “full cycle developers” within the Netflix edge engineering team. Following the principle of “operate what you build”, developers within this team chose to take on more operational responsibility for their services, and were facilitated by comprehensive tooling, training and management support.
-
Full Cycle Developers at Netflix: from Mindsets to Self-Service Tooling
The Netflix Tech Blog has shared the story of the “Edge Engineering” team’s journey of experimenting with approaches to building and operating services, which has culminated in “Full Cycle Developers”. This approach is showing promise with Netflix, where developers are responsible for certain operational aspects of service delivery, and are supported through a range of self-service tooling.
-
Trunk Based Development as a Cornerstone for Continuous Delivery
Dave Farley, co-author of the pivotal Continuous Delivery book, recently wrote about push-back to the practice of trunk based development, despite evidence of its role in achieving the benefits of CI and high performing teams. Jez Humble, his co-author, also commented in a twitter-thread on the cultural aspects of the practice to understand its relation to programmer psyche.