Related Content
3 Serverless Strategies to Look for in 2021 In this article, we examine the three serverless applications deployment and development approaches that are transforming the application development process and acting as a catalyst for fast adoption of the DevOps practice across the board. |
||
What Exactly Is Serverless? The word serverless—it’s everywhere. The word has been Googled an average of 100 times daily in 2020. Is serverless just a buzzword? A facade? Or a world where we won’t need servers anymore? |
||
Agile+DevOps Culture in a Virtual World Transforming and maintaining culture is hard enough when team members are somewhat co-located and in physical spaces—even harder when the majority are working from home. |
||
Balancing Testing and Delivery Times in Software Development So how can developers and their teams optimize testing procedures with the modern tools and tech available to them? Here, we will explore optimizing testing through experimentation to meet delivery deadlines and adapt to challenges in software development.
|
||
Test, Test, Test Test, test, test. This is a phrase that has caught everyone’s attention this year as we grapple to mitigate COVID-19. The WHO states that testing is the only way out, as we cannot fight the pandemic blindfolded. |
||
Evaluating Team Health in Agile and DevOps The importance of the human element in delivering great software is sometimes overlooked, as is the relationship between team health and team performance. Just like physical health checks, team checkups are important. Let's look at some factors that can affect team health and how you can evaluate the important metrics. |
||
Making the Most of Your DevOps: A Slack Takeover with Gene Gotimer Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Gene Gotimer, a senior architect at Coveros, hosted this Slack takeover and discussed all things DevOps, including whether you can have DevOps without agile and how you can reap all its benefits. |
||
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |