<story><title>Is it really “Complex”? Or did we make it “Complicated”? (2014) [video]</title><url>https://www.youtube.com/watch?v=ubaX1Smg6pY</url></story><parent_chain></parent_chain><comment><author>TheAceOfHearts</author><text>I haven&amp;#x27;t watched the video yet, so please forgive the possibly premature comment... But this is something that I&amp;#x27;ve found myself thinking about a lot lately. Are the things that we&amp;#x27;re currently building or maintaining truly that complicated or are we over-engineering things? I&amp;#x27;ve been humbled on more than one occasion where I initially thought an enterprise-y solution was over-engineered, until all the details of the problem were explained to me.&lt;p&gt;What I wish we had was a &amp;quot;man&amp;quot; equivalent to provide every-day examples of how to use the tool &amp;quot;correctly&amp;quot; (although I&amp;#x27;m aware there&amp;#x27;s stuff like &amp;quot;bro&amp;quot; pages), as well as another tool to explain why some tool &amp;#x2F; option even exists and how they&amp;#x27;re &amp;quot;expected&amp;quot; (by the creator &amp;#x2F; maintainers) to be used. As I&amp;#x27;ve gotten into the habit of reading man pages I&amp;#x27;ve become increasingly aware of how many options certain tools provide, but in many cases I really cannot fathom why those options are available or in what kind of situation they might be used.</text></comment>
<story><title>Is it really “Complex”? Or did we make it “Complicated”? (2014) [video]</title><url>https://www.youtube.com/watch?v=ubaX1Smg6pY</url></story><parent_chain></parent_chain><comment><author>perfmode</author><text>Is it theoretically impossible to fit an interpreter for a dynamic programming language in the L1 cache of a modern chip?&lt;p&gt;(I understand there are physical constraints that prohibit super low-latency memory lookups (of unconstrained size) in 0+epsilon time (where epsilon is small))</text></comment>