<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sunk-Cost-Fallacy on Scholion</title><link>https://scholion.thluiz.com/tags/sunk-cost-fallacy/</link><description>Recent content in Sunk-Cost-Fallacy on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/sunk-cost-fallacy/index.xml" rel="self" type="application/rss+xml"/><item><title>3 Types of Toxic Software Projects</title><link>https://scholion.thluiz.com/notes/3-types-of-toxic-software-projects/</link><pubDate>Mon, 20 Apr 2020 21:22:42 +0000</pubDate><guid>https://scholion.thluiz.com/notes/3-types-of-toxic-software-projects/</guid><description>The article says software teams should stop projects whose value no longer justifies their cost, whether they were misstarted, have become harder than expected, or are unused code that only adds complexity.</description></item></channel></rss>