Senior engineer at Dfinity. Technology leader with broad technical expertise in large-scale storage systems, reliability and security.
Have you come across engineering reports that make no sense? Take a look at the following examples:
• The organization has 98% test coverage, yet the product crashes and burns like a fiery wreck in the field.
• Teams deliver 100% of planned features, yet the release notes don’t reflect much progress. Or astonishingly, there are features in the release that nobody on the engineering team worked on.
• No bug fixes or other corrective actions went in, yet monitoring dashboards changed reporting to all green. Worse yet, engineering didn’t add anything, and testing pipelines all turned red.
For some, the above reports are puzzling, to say the least (for a few others, they are self-serving truths). In reality, 98% test coverage without testing the core 2% doesn’t amount to much. Hitting 100% feature complete without contributing to the how hard is computer science key success metrics (read revenue/unit-effort ratio) is vanity work. Making dashboards green by tweaking test pipelines doesn't change product reliability metrics.
Have you come across engineering reports that make no sense? Take a look at the following examples:
• The organization has 98% test coverage, yet the product crashes and burns like a fiery wreck in the field.
• Teams deliver 100% of planned features, yet the release notes don’t reflect much progress. Or astonishingly, there are features in the release that nobody on the engineering team worked on.
• No bug fixes or other corrective actions went in, yet monitoring dashboards changed reporting to all green. Worse yet, engineering didn’t add anything, and testing pipelines all turned red.
For some, the above reports are puzzling, to say the least (for a few others, they are self-serving truths). In reality, 98% test coverage without testing the core 2% doesn’t amount to much. Hitting 100% feature complete without contributing to the how hard is computer science key success metrics (read revenue/unit-effort ratio) is vanity work. Making dashboards green by tweaking test pipelines doesn't change product reliability metrics.
No comments:
Post a Comment