<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tech Debt on A Place for Poor Examples</title>
    <link>https://blog.mattblair.co/categories/tech-debt/</link>
    <description>Recent content in Tech Debt on A Place for Poor Examples</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 Sep 2023 15:22:57 -0800</lastBuildDate>
    
	<atom:link href="https://blog.mattblair.co/categories/tech-debt/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Decoding the Origins of CAN Reports</title>
      <link>https://blog.mattblair.co/blog/20230907-can-reports/</link>
      <pubDate>Thu, 07 Sep 2023 15:22:57 -0800</pubDate>
      
      <guid>https://blog.mattblair.co/blog/20230907-can-reports/</guid>
      <description>In the realm of incident management, accurate and swift communication is vital. Different organizations adopt various strategies to ensure efficient communication during emergencies. One such strategy that has been gaining traction is the utilization of CAN reports, a mnemonic that stands for “Conditions, Actions, Needs.” Let us delve deeper into the intricacies and origins of this unique reporting format.
What is a CAN Report? A CAN report, fundamentally, serves as a structure to relay critical information succinctly during an incident.</description>
    </item>
    
    <item>
      <title>Strategic Approaches for Technical Improvement</title>
      <link>https://blog.mattblair.co/blog/20230508-tech-improvement-roadmap/</link>
      <pubDate>Sun, 07 May 2023 12:19:57 -0800</pubDate>
      
      <guid>https://blog.mattblair.co/blog/20230508-tech-improvement-roadmap/</guid>
      <description>Introduction Technical debt is a common challenge faced by engineering teams, requiring deliberate efforts to manage and pay it down. In this blog post, we will explore different approaches to tackling technical debt and building a long-term technical strategy. We will also highlight the importance of involving senior individual contributors (ICs) and engineering managers (EMs) in shaping the strategy, while considering the alignment with business and product goals.
 Engaging Senior ICs and EMs in Technical Strategy  To ensure a comprehensive technical strategy, it is essential to involve experienced ICs and EMs in the decision-making process.</description>
    </item>
    
  </channel>
</rss>