<?xml version='1.0' encoding='utf-8' ?>
<rss version="2.0">
  <channel>
    <title>The Twilight Report</title>
    <link>http://www.wdlabs.com/twilight</link>
    <description>The Twilight Report - WhiteDactyl.com</description>
    <lastBuildDate>Fri, 25 May 2012 12:45:09 GMT</lastBuildDate>
    <generator>NX</generator>
    <image>
      <url>http://www.wdlabs.com/twilight/icon/twilight.jpg</url>
      <title>The Twilight Report</title>
      <link>http://www.wdlabs.com/twilight</link>
      <width>100</width>
      <height>100</height>
    </image>
      <item>
        <guid isPermaLink="true">http://www.wdlabs.com/twilight/entry/20110508.0919</guid>
        <pubDate>Sun, 08 May 2011 13:19:00 GMT</pubDate>
        <title>interviews</title>
        <link>http://www.wdlabs.com/twilight/entry/20110508.0919</link>
        <description>&lt;blockquote&gt;

Actually it’s worse than that. At least wide receivers have to run, whereas I can guarantee you, without fear of 
contradiction, that no software engineer will ever have to write a binary search after they are hired. It’s like choosing a 
contractor because they know how to forge and cast steel using coal, iron, an oven and a bellows, when they actually need to 
know a) the address of the nearest Home Depot b) what to do with the steel once they buy it.

&lt;/blockquote&gt;

&lt;p&gt;I found this interesting break down of technical interviews.  Somebody had posted the link on the SlashDot.  /. is this 
really exuberant misinformation farm by and for programmers and technical geeks.  Everyone there seems to know everything 
about everything even though their actual area of expertise is quite limited.  These conditions do provide some 
entertainment though, and every once and a while an interesting news item.  I have never seen them post anything about Bon 
Jovi though.  When I do post something I found on /. I usually post the original link though, not the cringe inducing /. 
posting out of fear of embarrassment.&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;&lt;a href=&quot;http://techcrunch.com/2011/05/07/why-the-new-guy-cant-code/&quot;&gt;Why The New Guy Can't Code&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;

&lt;p&gt;I agree with a lot about what he has to say, I have had those “how do you code a binary search” type questions, 
although not that exact one.  I would go further and say that the “how do you code a binary search” type questions 
inspires the sort of not-invented-here syndrome that tends to waste resources.  Annoying Cube Neighbour, for example seems 
to be trying to reproduce what Google is doing for search at a very low level, while everyone else is trying to fix bugs in 
a product that isn't in the same domain and needs to go out the door quick smart.&lt;/p&gt;

&lt;p&gt;I have had enough interviews now that I have gotten over most of the stumbling blocks. I don't mind wearing a tie or 
maybe a suit anymore, in fact I have noticed that it gives me a bit of a confidence boost, since I am almost always better 
dressed than my interviewers.  I should give a shout out here and say that this is entirely thanks to Lena.  Another huge 
advantage I have, not really in the interview itself, but in the process itself it are my references.  I usually have 
excellent references.  I know for a fact that I was their second pick at &lt;small&gt;s-mart&lt;/small&gt; until they spoke to my references, 
when I became the first pick.  Also when I was looking for a place to live, my future land-lady-at-the-time told me how 
highly my “friends”/references thought of me when she offered me the place.  That place in Beacon is still amongst my 
favourite homes.  It's a hard pick between it and the homestead in Wyoming though.  Anyway, I have some strengths in an 
interview, beyond at least some technical competence, but I have never quite got used to the idiot questions that people ask 
in interviews, although to be fair if the roles were reversed, I am not sure what questions I would ask to determine if 
someone was actually a competent coder.&lt;/p&gt;


&lt;p&gt;At my current position I had an interview question about OO-Perl which made me raise an eyebrow because it was so dumb, 
and also written in an unPerlish way.  In retrospect there were lots of warning signs that were just screaming “we don't 
know Perl”, but then when I interviewed at The Bureau, Mo asked lots of questions that had me rolling my eyes a little, and 
I think he is quite a good Perl programmer.  I feel like I am sort of in the reverse situation of the one described in the 
article.  Nobody at NetCon seems to be able to program easy to read, reusable Perl code.  Before you say “haha, easy to 
read, reusable Perl code is an oxymoron”, let me just remind you that I was spoiled at &lt;small&gt;s-mart&lt;/small&gt; and The Bureau, which 
were well run Perl shops where the code was 99% easy to read and much of it was reusable.  At NetCon they also dabble in a 
number of other technologies.  I'm hesitant to pass judgment on the code quality in those areas as I don't have as much 
experience.  If it weren't for the compensation package, I would be looking for a new job right now.  My Plan for World 
Domination&amp;trade; is still in effect, I still feel like there is a lot of opportunity here, &lt;i&gt;because&lt;/i&gt; nobody has yet 
learned the way of The Onion (that is a reference to Perl, not the satirical newspaper), but it is going to take me a while 
to crack the code.&lt;/p&gt;

</description>
        <comments>http://www.wdlabs.com/twilight/entry/20110508.0919</comments>
      </item>
  </channel>
</rss>


