{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"When Improving Processes Makes System Worse","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/cea663da\"></iframe>","width":"100%","height":180,"duration":340,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/when-improving-processes-makes-system-worse.\nWhy delivery failures rarely happen suddenly, and how small, reasonable decisions slowly create fragile systems long before incidents appear.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #software-engineering, #software-development, #systems-thinking, #software-reliability, #risk-management, #engineering-culture, #legacy-code, #legacy-systems,  and more.\nThis story was written by: @rfedorchuk. Learn more about this writer by checking @rfedorchuk's about page,\n            and for more stories, please visit hackernoon.com.\nMost delivery failures do not happen suddenly.\nThey emerge through small, reasonable decisions that slowly change how systems behave under pressure.\nUnderstanding delivery behaviour over time helps teams see risk before incidents force attention.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}