{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Architecture Decision Records (ADRs): A Beginner's Guide","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/9500af18\"></iframe>","width":"100%","height":180,"duration":719,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/architecture-decision-records-adrs-a-beginners-guide.\nWhat are Architecture Decision Records? Learn when to create ADRs, how to structure them, and the common mistakes engineering teams should avoid.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #software-architecture, #architecture-decision-records, #technical-writing, #documentation, #software-development, #system-design, #devops, #engineering,  and more.\nThis story was written by: @faithkovi. Learn more about this writer by checking @faithkovi's about page,\n            and for more stories, please visit hackernoon.com.\nArchitecture Decision Records (ADRs) document important technical decisions, the context behind them, alternatives considered, and their trade-offs. This guide explains when to create an ADR, how to write one, and where to keep it.","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}