Learning To Code Has Taught Me Nothing - 1

{{ story.headline }}

{{ story.subheading }}

{{ story.timestamp }}

Learning To Code Has Taught Me Nothing - 1
Note: This is part 2 in James Kotecki's ongoing saga You Should Learn To Code. He's planning on going from blogger to rockstar coder with nothing but Codecademy and a sense of humor.

Dear coders of the world,

How the hell am I ever supposed to catch up to you? Seriously, how?

I've been working in Codecademy for 10 days straight now, and you know what I've realized? I. Know. Nothing.

Sure, it feels like I've made a lot of progress. It was fun to blaze through HTML and CSS. Now I'm on to Javascript, where I've gained the ability to play Rock Paper Scissors with a computer. I even learned to rig the game so that I can pick 'Rope' and win every time. Awesome!

But it was right around this point that any hope of joining the ranks of professional hackers was dashed on the digital shoals of cyber reality. I'm pretty sure a bright 9-year-old could code at my level. And I'm making the computer do things I might have been amazed at in 1994, when I was nine.

But technology has progressed just a bit in the last 19 years. I've got some catching up to do. And 15 - even 30! - minutes on Codecademy every day probably isn't going to cut it.

It's not that I don't feel your support, coders of the world. I really do. Every computer literate person that I've told about this project has had nothing but positive, encouraging things to say.

But when they ask me if I've encountered [CODING THING I'VE NEVER EVEN HEARD OF] yet, I'm forced to tell them that I've never even heard of it. At my pace, by the time I do hear of it, self-aware computers will be able to program themselves and save us all the trouble.

I'll add those knowledge gaps to my list of known unknowns. I shudder to think of the unknown coding unknowns that I, Donald Rumsfeld-like, don't even know I don't know.

Ah, a political reference. Finally something I understand.