These are my original goals identified two months ago when I started this project:

Goal #1: Learn to code

Goal #2: Write a blog about my learning in order to process my thinking, share with other people, and gain insights from readers.

I have learned a great deal since I started working toward these goals almost 2 months ago, but have recently identified an unexpected outcome: I’ve begun to consume and process my technological experiences differently. (Clarification: This outcome was unexpected to me…not necessarily anyone else!) Continue reading →

I love Halloween! The whole spirit of the day is so refreshing and whimsical. Everyone has fun, and there are few family or religious obligations attached. (…obligations that can make other holidays more stressful!) Plus, if you happen to be a Halloween grinch, all you have to do is make sure your porch light is off, and Viola! You have the perfect excuse to curl up in your basement with a good book or a movie and ignore the world for a night. Halloween is a win-win.

One of my favorite parts about the holiday is that it gives all of us over-worked, over-tired, over-stressed, and entirely-too-serious adults an excuse to just take a breath and to think like children for a day. We can delight in the excitement of the little ghosts and goblins (and Elsa’s and Spidermen) that haunt our streets for just one night every year We all get to have fun, forget our troubles, and pretend we are someone else. We can adopt a sense of wonder and just PLAY! Continue reading →

Codecademy environment, Ruby Tutorial…Left is instructions, center is where you type the code, and right is where you see the program run.

As I’ve been making my way through tutorials, something was starting to bother me. Tutorials let you practice in nice little environments that provide three fields: One for the tutorial’s instructions, a second for you to write code, and a third to show the results of your programs.

The problem is…This all happens on a webpage, and I couldn’t figure out how that translates to writing actual code and having it do something on my real computer. If I don’t know this, I would bet that others as green as me don’t really know either. Thus, I decided to figure it out (with help of course), and spell it out in this post. Maybe this will be helpful to other novices out there, and I know it will be helpful to me in the future if I need a reminder.

I asked my most trusted advisor, the husband, how to program something for real, and he explained the steps you need to go through. The “Hello, world!” program seems to be an initiation ritual of sorts, so I decided to use my little “programming for real” lesson to make my computer say “Hello, world!”

Ruby has quickly become my language of choice. There’s something about it that just draws me. It might be because I’ve started reading “Why’s Poignant Guide to Ruby”, and he agrees it’s important to submit to something that draws you.

Not familiar? Here’s a passage:

“This world’s too big for such a a little language, I thought. Poor little thing doesn’t stand a chance. Doesn’t have legs to stand on. Doesn’t have arms to swim.”

Like when you meet Somebody in college and they look like somebody who used to hit you in the face with paintbrushes when you were a kid. And so, impulsively, you conclude that this new Somebody is likely a non-friend. You wince at their hair. You hang up phones loudly during crucial moments in their anecdotes. You use your pogo stick right there where they are trying to walk!

I’ve been at my self-challenge of learning to code for a few weeks now. I figured it was time for some self-reflection on what I’ve actually been doing, because I’ve been doing a lot of different things including online tutorials, human interaction, reading, and self-reflection. Part of me feels really good about what I’ve been doing, and part of me feels concerned that I’ve going about this in the wrong way. Is this how it always feels when you decide to learn something completely foreign and hard?

So far, I’ve played with lots of different strategies for learning. I really like bulleted lists, so I’m just going to make a whole bunch that detail my attempts at learning to code:

I signed up for Code Academy about a week ago to access tutorials for JavaScript and Ruby, and I like how they email me little messages every once in a while. The funny thing is, I’m not usually a fan of this. I can’t stand arbitrary marketing emails, and with the November election coming up, my political affiliations are trying my patience! Anyway, I actually enjoy the little messages from Zach Simms, CEO of Codecademy.

I have been questioning which language to focus my novice coding energy on, and have concluded that I need to figure out a couple things:

Which language feels easiest to me

Which will help me do the things I want to do

Yesterday, I decided my mission is to figure out something I want to do in order to address the second question. Well, it’s like Zach psychically picked up on my thoughts, (and I know that’s what internet marketers everywhere want me to think), because I awoke to find a very helpful little message in my inbox this morning, and thought I would share!

Via Zach Simms, CEO of Code Academy:

People often ask me what programming language they should learn, and I always say the same thing: “It depends.”

Want to be more web savvy, or build a website? — start with Web Fundamentals. This covers all the basic HTML and CSS you’ll need to know to understand the web.

Want to make a game or app? — give JavaScript a try. This dynamic language will let you create interactive apps that you can use on a smartphone.

Want to process data or explore databases? – Ruby or Python are your best bet.

“You should have a look at LOGO, the turtle graphics language. Here is a link to a very good site for this, with interactive action”: http://turtleacademy.com/index.php(Comparing Logo to Ruby, he goes on) “The Logo turtle graphics is more fun, and will develop your understanding very quickly. It will do arithmetic, but its main purpose is to move a “turtle” around the screen, drawing or just moving, by specified amounts. the tutorial stuff is excellent.”

This is why I love crowdsourcing! I never would have thought of Logo, but I remember it! I think I was exposed to it sometime in middle or high school the 90s. I can’t remember too many details, but the memory is enough to give me SOME kind of reference point for this thing called coding.

I took the advice and started playing with this little tutorial, and realized this was perfect because it really taps into interest-based learning for me.