I believe the intent there, was that if you have difficulty learning new syntax for the same basic logical operations and structures, then programming probably isn't for you.
Personally, I can "Read" almost any structured language. (Almost. Perl and pals are alien dialects intended for alien minds. thankfully, NOBODY writes games in perl. Not unless they are masochists.)
The idea is that the language basically is just the vehicle for the logic, and without understanding and being intimate with the mindset and thinking needed to use logic in that way, being fluent in the language is rather pointless. (To whit, the scores of entry level code monkeys that cant pass the fizzbuzz/fizzbang test.)
Basically, the syntax is perfect, with perfect convention--- but the code is terrible. Looking through some industrial automation scripts, I have seen my fair share of this. One of my co-workers has a string parsing algorithm for taking APT statements from CAM packages, and mangling it into NC code structures. It is painfully slow, because it is inefficient. I can see that it is inefficient, and why it is inefficient, but despise doing computer programming work, as it causes me acid indigestion. There is nothing wrong with his syntax, but the actual program is poorly devised. I believe that is what the GP was meaning.
*on topic of the OP*
I suppose I could make myself a small gallery of random artsy bits I have cooked up, but most of them are just silliness, with no intention of being professional, since I approach the art from a non-professional angle. i think a better way to see what I can actually do when I put the pressure on, would be to give me a small challenge for asset creation, and then see what I make. Judge from that if you want to consider putting me on the rolodex or not. I'd consider that a fair cop. (i've done similar things for my employer, where I have created semi-realistic looking solid representations of our CNC equipment and workcenters, for floor plan restructuring and planning purposes. Try modeling up an entire factory in a week. Been there, done that.)
I'm happy to show you what I can do, but again, I need a well established set of goals and deadlines, with specific and listed items to be made, and when they need to be made by if I am actually going to work in a team structure. Just give me a random list of crap, and I'll see what I can to.