<story><title>Speed matters: Why working quickly is more important than it seems (2015)</title><url>http://jsomers.net/blog/speed-matters</url></story><parent_chain><item><author>koonsolo</author><text>40 year old here. Speed doesn&amp;#x27;t matter as much as WHAT you deliver. First of all, people do not know how much time something takes. And secondly, they will forget how much time it took, but not how well it was made.&lt;p&gt;Responding fast to emails is just crazy. I lost count on how many urgent problems got resolved automatically. &amp;quot;Hey can you help me with this&amp;quot;. 15 minutes later &amp;quot;Nevermind, found it&amp;quot;.&lt;p&gt;I&amp;#x27;m in the &amp;quot;Slow is smooth, smooth is fast&amp;quot; camp. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.lesswrong.com&amp;#x2F;posts&amp;#x2F;4FZfzqMtwQZES3eqN&amp;#x2F;slow-is-smooth-and-smooth-is-fast&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.lesswrong.com&amp;#x2F;posts&amp;#x2F;4FZfzqMtwQZES3eqN&amp;#x2F;slow-is-sm...&lt;/a&gt;</text></item></parent_chain><comment><author>markbnj</author><text>&amp;gt; And secondly, they will forget how much time it took, but not how well it was made.&lt;p&gt;Absolutely. Not saying speed is never an important metric, but virtually all complicated engineering and construction projects are difficult to schedule and exceed their time budgets. If the end result is worth it those birthing pains are quickly forgotten. But a poor output will never be forgotten.</text></comment>
<story><title>Speed matters: Why working quickly is more important than it seems (2015)</title><url>http://jsomers.net/blog/speed-matters</url></story><parent_chain><item><author>koonsolo</author><text>40 year old here. Speed doesn&amp;#x27;t matter as much as WHAT you deliver. First of all, people do not know how much time something takes. And secondly, they will forget how much time it took, but not how well it was made.&lt;p&gt;Responding fast to emails is just crazy. I lost count on how many urgent problems got resolved automatically. &amp;quot;Hey can you help me with this&amp;quot;. 15 minutes later &amp;quot;Nevermind, found it&amp;quot;.&lt;p&gt;I&amp;#x27;m in the &amp;quot;Slow is smooth, smooth is fast&amp;quot; camp. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.lesswrong.com&amp;#x2F;posts&amp;#x2F;4FZfzqMtwQZES3eqN&amp;#x2F;slow-is-smooth-and-smooth-is-fast&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.lesswrong.com&amp;#x2F;posts&amp;#x2F;4FZfzqMtwQZES3eqN&amp;#x2F;slow-is-sm...&lt;/a&gt;</text></item></parent_chain><comment><author>api</author><text>Another 40 year old here: I mostly agree and I&amp;#x27;ve also found that thinking deeply about a problem for a long time before trying to build anything pays huge dividends. In particular I spend a long time thinking about how I can simplify the design to save implementation time, which means actually building it is faster. I also think a lot about UX and DX: simplifying installation, interface, maintenance, removing unnecessary knobs, choosing the right algorithms and tooling, etc.&lt;p&gt;I think waterfall style development works for one person inside one&amp;#x27;s own mind, but not beyond that.&lt;p&gt;A lot of the stuff I see from 20 year olds these days is monstrously over-engineered and Rube-goldberg like. Many keystrokes, sure, but less thought. This also yields bloatware that hogs resources and is hard to install and maintain.&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.ariel.com.au&amp;#x2F;jokes&amp;#x2F;The_Evolution_of_a_Programmer.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.ariel.com.au&amp;#x2F;jokes&amp;#x2F;The_Evolution_of_a_Programmer....&lt;/a&gt;&lt;p&gt;More thought and less typing young padawan.</text></comment>