<story><title>Systems thinking as important as ever for new coders</title><url>https://www.hanselman.com/blog/SystemsThinkingAsImportantAsEverForNewCoders.aspx</url></story><parent_chain></parent_chain><comment><author>bluejellybean</author><text>Systems thinking is, by far, my favorite mode of thinking. It&amp;#x27;s why I love programming, business, biology, mathematics, aerospace, etc... I&amp;#x27;m convinced that being able to think about abstract systems fluidly is a core skill that separates the good from great in many fields and this is probably more so true in software. I really wish there were better resources for building up this skill set. I was gifted with a decent intuition for it and gained a lot from engineering courses, but I just haven&amp;#x27;t found anything specific that I can point a junior engineer towards and say &amp;quot;This, this is the essence of systems thinking!&amp;quot;. The closest thing I&amp;#x27;ve found is a lecture series on the space shuttle design[0], and while the series is fantastic, it doesn&amp;#x27;t focus on the core idea of systems thinking. Does anyone have any useful resources or  recommendations on the subject?&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;ocw.mit.edu&amp;#x2F;courses&amp;#x2F;aeronautics-and-astronautics&amp;#x2F;16-885j-aircraft-systems-engineering-fall-2005&amp;#x2F;video-lectures&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;ocw.mit.edu&amp;#x2F;courses&amp;#x2F;aeronautics-and-astronautics&amp;#x2F;16-...&lt;/a&gt;</text></comment>
<story><title>Systems thinking as important as ever for new coders</title><url>https://www.hanselman.com/blog/SystemsThinkingAsImportantAsEverForNewCoders.aspx</url></story><parent_chain></parent_chain><comment><author>satyenr</author><text>Well said. I have come across candidates looking for engineering positions with a laundry list of fancy technologies they claim to have have worked on — yet can’t answer simplest questions about the fundamentals — way too often for my liking. There seems to be an inherent assumption that one just needs to be able to operate the newfangled technology of the day to be an engineer. Who needs to know about how network calls are made or the mechanics of spawning processes&amp;#x2F;threads — there are libraries to abstract all that.</text></comment>