>Why should it be good for me to work with somebody who only cares about Java? And what would you take about during lunch - Java development? Knowledge depth,

>Why should it be good for me to work with somebody who only cares about Java? And what would you take about during lunch - Java development? Knowledge depth, for one. The time you spend reading about new trends and languages is time not spent getting deeper knowledge about the skills you already have. Maybe you spend just as much time as he does gaining knowledge depth in your chosen language and spend some of your free time reading about trends and languages, whereas he might spend time with his family instead. You're still basing this decision on an arbitrary signal like "Reading about trends and languages makes you a better programmer", which is a very difficult thing to prove, the least of all reasons being that there are no hard lines drawn in the sand regarding programmer skill levels and the positions that they qualify for. But then someone with this same attitude comes along and reads about trends, languages, and computer science developments. That guy won't hire you because you don't read about computer science developments because he thinks those three sources of knowledge makes you an even better programmer. He spends the same amount of time gaining knowledge depth as you do, but spends even more time reading about trends, languages, and CS developments, regularly sacrificing an hour of sleep. And then someone comes along and reads about trends, languages, CS developments, and hardware hacking[, and social engineering][, and UI/UX theory][, and mathematics developments]. You can see how this can quickly fill someone's entire waking hours in a rat race to be the guy casting down judgment. >Back to Joel: it seems more likely that somebody who knows Joel is a good programmer than somebody who doesn't know Joel. You can hang around forums and parrot whatever other people are talking about and blend in without ever having to elaborate or think about Joel's blog (not to mention actually practice any of it). This is the same sort of signalling that SV is using according to the article. I know about Jeff Atwood and his famous Fizzbuzz post. If you do a bit more reading, you know that it's not actually meant for the technical aspects: http://blog.codinghorror.com/fizzbuzz-the-programmers-stairway-to-heaven/ http://blog.codinghorror.com/fizzbuzz-the-programmers-stairw... Having that bit of knowledge quickly skyrockets my perceived skill level above "the crowd". I'm an insider now, someone to get a little excited about hiring, and for no more work than it took to read a blog. Then I start rattling off other things I've seen on here, reddit, and other places that make me seem intelligent and well-read. Now they're tittering to give me an offer. Then they get a nice dose of reality when they learn I'm still pretty new with regards to actual skill. If I wanted to be an SV insider, I'd follow the same procedure: read about what signals they are looking for, mimic those signals, and play it by ear the rest of the way. I guess if I had to code actual projects to make it then I can't be as deceptive because I'll actually know how to do something. (To save some of my dignity, I actually have done that!) This is job hiring through obscurity.