<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Estimation on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/estimation/</link><description>Recent content in Estimation on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Thu, 28 May 2026 12:00:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/estimation/index.xml" rel="self" type="application/rss+xml"/><item><title>Here's Why You Should Start Estimating in Complexity Instead of Hours | HackerNoon</title><link>http://karpoke.ignaciocano.com/2026/05/28/here-s-why-you-should-start-estimating-in-complexity-instead-of-hours-hackernoon/</link><pubDate>Thu, 28 May 2026 12:00:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2026/05/28/here-s-why-you-should-start-estimating-in-complexity-instead-of-hours-hackernoon/</guid><description>&lt;blockquote&gt;
&lt;p&gt;There&amp;rsquo;s a quiet truth every developer knows, but nobody says out loud at
sprint planning: When we estimate in hours, we always estimate low.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/heres-why-you-should-start-estimating-in-complexity-instead-of-hours"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>