Scoble points to Segal giving advice to 'Go code something' as a way to get hired. let me just say that this does not work ... at least not directly. because i've been trying this methodology for the last 5 years. during those 5 years i've tried to code something cool about every 1 or 2 months. the idea was that companies would see the tech article and contact me to work for them. over those 5 years and around 10 contracts ... only one of those has been a direct contact from an article i've written. actually there were 2 ... but it was for a smaller contract and the guy never bothered to pay me ... bastard.
not that i haven't had a number of direct contacts, but they always fall through. MS has contacted me a couple of times to become an employee. the first time was early on from a recruiter search. they wanted me to do SQL Server testing ... lame. the second time was rumored to be one of their tech giants saying they should hire me for an evangelist position. did the interview ... and they said no. they've also contacted me numerous times to hire on their consultancy team ... to which i just tell them i can do that myself. MS has also contacted me a number of times for contract work. they either fail because they want me to travel for substantially less money than i could make at home or everything goes great and they say they'll contact me in 2 weeks ... but i never hear from them again. outside of MS, i get about 1 contact a month from the /cfWorldWind article ... but nothing has happened yet. also get at least 1 contact a week from the /aiCaptcha article. but i'm not particularly interested in working with those guys.
so the direct route from coding something cool to finding work is a sham. and the reason it does not work is because of the disconnect between the employees that can actually appreciate what you have coded and the recruiters that will contact you. and that is how i actually do find work ... recruiters. for every direct contact ... i get about 15 recruiter calls. the recruiters have no freakin clue what i code. they cant tell the difference between AI vs a web app. they dont know the diff between an MVP and an MCSD. all they care about is how much they can make off of me. and they are really the only obstacle to work. the way i look at it is if i can get past the recruiter and talk to the hiring company ... then its a sure thing. but trying to get past the recruiters is a pain in the butt. they can easily not submit you in favor of somebody that they can make more money off of ... go figure.
then the question is ... why do i still code all this crap. answer : because i love to code. the articles i write are about what i want to learn ... they aren't really for you or anybody else. but they do indirectly help for finding work. when i do get past the recruiter to talk to the hiring company, then its pretty much a done deal. meaning i hardly ever get tech interviewed anymore. basically they just look at my articles, and then we just talk about their problem and when can i start. my advice is to code something if you love to code, otherwise get out there and network your ass off. your friends will do a better job of helping you find work then most code that you'll write. granted, i do make alot of friends through code ...