(public).sospep.subjects ~ view article ~ death-to-the-tech-interviews

<h1 style="text-align: center;">title</h1>
<h2>[WHAT]</h2>
<ol>
<li>] <a href="http://blog.iambob.me/death-to-the-technical-interview/" target="_blank">http://blog.iambob.me/death-to-the-technical-interview/</a>&nbsp;</li>
</ol>
<h2>[WHY]</h2>
<ol>
<li><strong>]&nbsp;<span style="text-decoration: underline;">coding is hard</span>.</strong> coding while a potential future employer is scowling over your shoulder and murmuring inaudibly makes the process incalcuably harder.</li>
<ol>
<li>So, allow me to tell you why we all should join the chorus calling for the death of the modern technical interrogation.</li>
</ol>
<li><strong>]&nbsp; It's not a good indicator of technical ability</strong></li>
<ol>
<li>&nbsp;in what possible high-pressure situation will you ever be expected to solve an obscure data structures problem on a whiteboard. With no syntax checking or debugger. In front of three scrutinizing neck-beards. Answer: Never.</li>
</ol>
<li><strong>] solutions to seperate the Michael Jordans of coding from the not Michael Jordans</strong></li>
<ol>
<li>github profile -</li>
<li>programming project -</li>
</ol>
<li>] It's unpleasant for all involved</li>
<ol>
<li>a bad tech interview is bad for both sides -</li>
</ol>
<li>] Questions are hard to craft? Questions <em>are</em> hard to craft.</li>
<ol>
<li>questions need to be tailored to the candidate being interview</li>
</ol>
<li>&nbsp;</li>
</ol>
<h2>[WHERE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>]</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>]</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] networking FROM [ Book] strategy-technology IN [ libraries] technology