In this conversation for The New Stack Makers, Majors discusses a number of themes relating to observability and monitoring, as well as how she continues to make herself a better developer. The topics include how: Test-driven development and how it has evolved. Monitoring as a practice — much like test-driven development — was built for on-premises architectures. Observability is the successor to monitoring by allowing for the discovery of the “unknown, unknowns,” which Majors previously wrote is like “following breadcrumbs to find what you don’t even know what is there.” A robust architecture is required for observability. While observability has been referred to as a “missing link” in DevOps, Majors said, instead, “it’s not such a missing link as it is a necessary first step.”
In this conversation for The New Stack Makers, Majors discusses a number of themes relating to observability and monitoring, as well as how she continues to make herself a better developer. The topics include how:
Test-driven development and how it has evolved.
Monitoring as a practice — much like test-driven development — was built for on-premises architectures.
Observability is the successor to monitoring by allowing for the discovery of the “unknown, unknowns,” which Majors previously wrote is like “following breadcrumbs to find what you don’t even know what is there.”
A robust architecture is required for observability.
While observability has been referred to as a “missing link” in DevOps, Majors said, instead, “it’s not such a missing link as it is a necessary first step.”