<story><title>Netflix announces Space X documentary on civilian mission into orbit</title><url>https://news.sky.com/story/netflix-announces-space-x-documentary-on-civilian-mission-into-orbit-12372247</url></story><parent_chain><item><author>spikels</author><text>Came here to post that video. Awesome!&lt;p&gt;My favorite part:&lt;p&gt;Elon&amp;#x27;s 5-Step Design&amp;#x2F;Development Process:&lt;p&gt;(1) Fix &amp;quot;Dumb&amp;quot; Requirements&lt;p&gt;(2) Remove Unnecessary Parts&amp;#x2F;Processes&lt;p&gt;(3) Simplify&amp;#x2F;Optimize&lt;p&gt;(4) Speed Up Cycle Time&lt;p&gt;(5) Automate</text></item><item><author>InTheArena</author><text>The recent interview of Elon by Tim Dodd is probably more informative and interesting this this could ever be.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=t705r8ICkRw&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=t705r8ICkRw&lt;/a&gt;</text></item></parent_chain><comment><author>__sy__</author><text>I thought this was an absolutely masterful explanation of engineering design thinking. If I may, I would also like to add to this list another thing he mentioned: &amp;quot;each requirement must have a name attached to it.&amp;quot;&lt;p&gt;I believe he was referring to the first step. And &amp;quot;Name&amp;quot; was really &amp;quot;a person&amp;quot; as opposed to &amp;quot;a department.&amp;quot; This was his way of saying DRI all the way down to each individual requirements, to force someone to be accountable for it. His example was that SpaceX interns previously listed requirements, that were later assigned to a department (e.g. avionics), and when prompted, no one in that department really knew why it was there.</text></comment>
<story><title>Netflix announces Space X documentary on civilian mission into orbit</title><url>https://news.sky.com/story/netflix-announces-space-x-documentary-on-civilian-mission-into-orbit-12372247</url></story><parent_chain><item><author>spikels</author><text>Came here to post that video. Awesome!&lt;p&gt;My favorite part:&lt;p&gt;Elon&amp;#x27;s 5-Step Design&amp;#x2F;Development Process:&lt;p&gt;(1) Fix &amp;quot;Dumb&amp;quot; Requirements&lt;p&gt;(2) Remove Unnecessary Parts&amp;#x2F;Processes&lt;p&gt;(3) Simplify&amp;#x2F;Optimize&lt;p&gt;(4) Speed Up Cycle Time&lt;p&gt;(5) Automate</text></item><item><author>InTheArena</author><text>The recent interview of Elon by Tim Dodd is probably more informative and interesting this this could ever be.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=t705r8ICkRw&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=t705r8ICkRw&lt;/a&gt;</text></item></parent_chain><comment><author>inglor_cz</author><text>Two things I took from that interview:&lt;p&gt;* the quip about people spending a lot of time to optimize something unnecessary,&lt;p&gt;* the quip that you must be wary about recommendations made by smart people, because you will tend to trust smart people too much and they can still make mistakes.</text></comment>