1 Why the nerdy properties in us makes us worse at coding.
  2
  3 Let's just define a Nerd according to this Venn diagram as a person with a hint of Intelligence, Obsession and Soci    al Ineptitude. Src: http://i192.photobucket.com/albums/z167/Great_WhiteSnark/Nerd_Dork_Geek_Venn_Diagram.jpg.
  4
  5 When discussing coding online and reading coding related articles on Hackernews and Slashdot, my preferred 'nerd' s    ources of reading I commonly get drawn into the most common topics which usually hover around two different themes:     Why framework/langunage X is good and how a successful company solved problem X (with technical details included).
  6
  7 The problem with the first one is usually that discussions always are biased by factors not depending on the core l    anguage and most of the examples are taken from one good/or bad experience, not a large statistical pool at all.
  8
  9 The reason that the second topic of discussion wont get you anywhere is that it only shows and example of what tool    s were used to solve the problem. Even if you used the same tools, your problem/colleagues and many other factors w    ill not be the same therefore making this agument null.
 10
 11 But why do people both online and 'in the job' usually show an amazing interest of discussing these two topics?
 12
 13 I will tell you, it comes from the properties of some people described earlier as nerds, and their ability to with     their intelligence gather information on how to solve problems and since they have an inner need to be seen as smar    t problem solvers and not just as the persons they are (since the social ineptitude) they greedily search for a hol    y grail, and when they think they found it they get obsessive around it.
 14
 15 What if they would drop the cloud that fogs their mind and only think of what really makes things work?
 16
 17 They would probably realize that sound software engineering would be really "uncool" and rely on not only technical     factors where the lonley geek can save the world with his obscure knowledge of some techonology but mainly on stuf    f like teamwork, testing, good planning, good bosses and a great personality to get work done.
 18
 19 Thats why I personally usually enjoy focusing on the "obvious" details as noted by the Joel test where you ask your    self if your company fills these criterias:
 20
 21 Do you use source control?
 22 Can you make a build in one step?
 23 Do you make daily builds?
 24 Do you have a bug database?
 25 Do you fix bugs before writing new code?
 26 Do you have an up-to-date schedule?
 27 Do you have a spec?
 28 Do programmers have quiet working conditions?
 29 Do you use the best tools money can buy?
 30 Do you have testers?
 31 Do new candidates write code during their interview?
 32 Do you do hallway usability testing?
 33
 34 My advice to you out there would be, go back to basics! How? Search the answer within yourself.