i remember the first time i heard that statement - a couple years back eric florenzano said it to me on twitter when i posted my resume publicly and asked for opinions. at the time i laughed at his statement, because it felt like naive arrogance to ditch the idea of a resume and 'traditional' social networking like facebook and linkedin. how wrong i was...

before i go any further, this isn't to say that education, job history, and references aren't important in getting jobs that utilize a lot of python. they are important, but i think they go more towards shaping you as a person than getting a job. so if you want access to python jobs (and possibly other open source languages), you need to be able to show working code. why is this the case? i can thing of several reasons:

1. it is much harder to forge your style of code, comments, tests, and docs in a repo than it is to make false claims on a resume.
2. development team managers don't take linkedin references seriously because how often we see them gamed.
3. code gives us a body of work employers (including me) can use in order to help evaluate your skill and ability levels.

let's summarize that into a bold statement:

python employers want to review your code in a public repo.

that puts the pressure on you doesn't it? now you've got to show working code. one extremely unethical way to do that is to copy/paste other people's code into your own repo and claim it as your own. the problem with that is real reviewers know good code doesn't just magically appear in gigantic chunks. which i'll sum up with another statement:

python employers are smart enough to read your commit log.

so as a beginner, what can you do? a lot of shops will want to see your code but if you put up your early code, doesn't that mean they'll see your ugly, mistake-ridden work? yes they will - but if you keep at it with tutorial examples you are working, whatever pet project you cook up, or even submitting patches to various existing projects, they'll see how your code improves. i am much more inclined to hire a person able/willing to learn than a jaded expert who doesn't want to grow - which is why i always try to think like an eternal beginner. which brings me to my third statement:

python employers are willing to hire bright, hungry developers willing to learn.

getting away from employment, let's talk a little about the python development community. this community is a meritocracy with amazing foresight. passion for code and/or natural talent is often recognized before skill is achieved - but only if you show the community you are learning. get your code onto github, or bitbucket, or sourceforge so it is seen, and keep at it! try to commit every day and if that isn't possible, then once a week!

because if you write code every day or every week, over time your code will get better, you'll also be able to demonstrate a consistent body of work, and your passion for software development will be obvious. also, try to comment your code as much as possible.

one good trick is to put your ongoing notes in a repo. i do it myself athttps://github.com/pydanny/pydanny-event-notes. my early notes are very, very different from my later notes. often embarrassingly so, but to a python employer i'm pretty certain they are a useful reference into just how i think.

github, not linkedin

linkedin (and facebook, google plus, et al) are a place to define your profile and nothing more. that profile should include a link to your code. python employers will be looking your for links to your code, not for any sort of networking you do on those sites. employers get annoyed by 'developers' who excessively network but have no links to code samples on github or other similar sites. if you have no code to find then it means we can't see your work, your thought processes, or your passion. 

one common technique you see by a lot of python developers is posting quick links to their projects and efforts on github using various social networks. you can and should do the same.