Here&#x27;s what the article claims is the problem:<p><pre><code>   Samsung&#x27;s upper management
   just inherently doesn&#x27;t understand software
</code></pre>
Which can be said about a lot of companies.<p>When I think of how management at hardware companies selects engineers to work on software, I&#x27;m reminded of this AAMCO commercial.
<a href="http:&#x2F;&#x2F;autoweek.com&#x2F;article&#x2F;classic-ads&#x2F;horror-stories-malaise-era-aamco-commercials" rel="nofollow">http:&#x2F;&#x2F;autoweek.com&#x2F;article&#x2F;classic-ads&#x2F;horror-stories-malai...</a>
In the fifth commercial clip, there&#x27;s a yokel putting water into a radiator. When he hears that there&#x27;s a transmission to fix, he says:<p><pre><code>   Let me try, boss!
   I always wanted to fix a transmission.
</code></pre>
Software engineering is much different than hardware engineering. That doesn&#x27;t mean that one person can&#x27;t do both. But that person needs to have read some good CS books and taken some CS courses (IMO). Of course there will always be hardware guys who just skim thru the book Software Engineering for Dummies. And they&#x27;re the ones who do a poor job.<p>It&#x27;s the same mentality that we saw with the Toyota unintended acceleration software.[1] E.g., &quot;spaghetti code&quot; and more than 10,000 global variables.<p>Disclaimer: I majored in CS in college, but I&#x27;ve designed a lot more hardware in my life than I&#x27;ve written code. So I&#x27;m really the opposite, a software guy who tried his hand at hardware. :)<p>[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9643551" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9643551</a>