The author argues against the term "technical debt," suggesting it diminishes the seriousness of unresolved problems in software development. Instead, they advocate for calling such issues "mess," implying a need for accountability and clarity in recognizing problems that arise from decision-making.