What is a common practice by teams who have embraced DevOps?

A common practice embraced by teams that have adopted a DevOps culture is conducting blameless postmortems. This approach emphasizes learning and improvement after incidents or failures rather than assigning blame to individuals. By focusing on understanding the root causes of issues, teams can foster an environment of collaboration and trust, which is essential for continuous improvement. This practice encourages open communication where team members feel safe discussing what went wrong without fear of repercussions, ultimately leading to better solutions and enhanced operational resilience.

In contrast, the other options reflect practices that are not aligned with the principles of DevOps. For instance, a conservative programming approach may hinder innovation and rapid iteration, which are key components of DevOps. Working all night suggests burnout and a lack of work-life balance, which goes against the DevOps tenet of sustainable practices. The use of IRC chat, while it may facilitate communication, isn't a defining or common practice of DevOps and can be considered outdated compared to more integrated communication tools that support collaboration in modern DevOps environments.