Engineering Practices for Achieving Stability- Episode 26

Programming with Palermo

In this episode, Jeffrey discusses the suggested engineering practices for achieving stability. After establishing quality, achieving stability is the next pillar in the Clear Measure Way along the path to increasing speed. Without stability, the software team will always be devoting some portion of its capacity to diagnosing and fixing stability issues with the software in production.

• Priorities

  • Prevent production issues
  • Correct production issues quickly

• Stability practices

  • Automated deployments
  • formal release candidates
  • low-maintenance environments
  • Runtime automated health checks
  • production-like pre-production environments
  • explicit secrets management
  • centralized logging
  • custom application metrics & events
  • distributed tracing
  • APM tool with an operations dashboard
  • anomaly alerts
  • emergency alarms
  • formal support desk w/ ticket tracking

Sample repository

Thanks to Clear Measure for sponsoring this sample and episode of Programming with Palermo.

This program is syndicated on many channels. To send a question or comment to the show, email [e-mail]. We’d love to hear from you.

To use the private and confidential Chaplain service, use the following Gentleman: 512-619-6950 Lady: 512-923-8178