(public).sospep.subjects ~ view article ~ how-to-pass-a-programming-interview

<h1 style="text-align: center;">how to pass a programming interview</h1>
<h2>[WHAT]</h2>
<ol>
<li>] by Ammon Bartram@triplebyte.com -&nbsp;being a good programmer requires solving large problems over a longer period of time. passing a programming interview requires solving smaller problems quickly while explaining clearly what you are doing.&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>]&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>]&nbsp;<a href="http://blog.triplebyte.com/how-to-pass-a-programming-interview" target="_blank">http://blog.triplebyte.com/how-to-pass-a-programming-interview</a></li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2016-03-08</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li><strong>]&nbsp;Be enthusiastic</strong></li>
<li><strong>]&nbsp;Study common interview concepts&nbsp;</strong></li>
<li><strong>]&nbsp;Get help from your interviewer&nbsp;</strong></li>
<li><strong>]&nbsp;Talk about trade-offs&nbsp;</strong></li>
<li><strong>]&nbsp;Highlight results&nbsp;</strong></li>
<li><strong>]&nbsp;Use a dynamic language, but mention C</strong></li>
<li><strong>]&nbsp;Practice, practice, practice&nbsp;</strong></li>
<li><strong>]&nbsp;Mention credentials&nbsp;</strong></li>
<li><strong>]&nbsp;Line up offers&nbsp;</strong></li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] SRC = HN, <a href="https://news.ycombinator.com/item?id=11246917" target="_blank">comments</a></li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] index FROM [ Book] analysis IN [ libraries] careers