There was a time when I wasn't confident enough to do that, and would avoid new languages/frameworks/whatever, because I didn't 'know' them. I am so much better now for having moved past that.
I think I agree more with the feel of the article than the actual statement. If his point is to say that you should persist even if you aren't perfect at something, then absolutely. If he's saying you should just write bad code and not worry about it, obviously, I disagree.
But when you start, you always write bad code. I learned python a few weeks ago for a pipeline for an iphone game I'm making. I'm learning Objective C right now. I know a lot of what I've written is probably crap -- but as I write more, I realize what was crap and fix it when I bump in to it.
The learning mindset is more important than the "stubbornly move forward" mindset. His skull demo example is a good story. If that person never learned another thing, he would eventually be driven insane by trying to deal with the complexity of a large scale project. If he learned ways to improve, moving forward, he could continue building even bigger and better bleeding skulls.
