28 thoughts everyone* has when learning to code via a manual.

*Ok fine, thoughts that I have.  But I hope there are other people who have similar thoughts.

Learning is all about the presentation.  The difference between information given in a popular “written-for-the-masses” non-fiction book and an online manual is astounding.  I could read those non-fiction books for days straight without pause (except maybe some food and bathroom breaks). But a written tutorial?  Hoo boy.  Don’t even expect me to pick it up until after I’ve browsed the entire internet, ate about 2,000 calories worth of snacks, and read 300 pages of the fun book I’m reading on the side. Yep, presentation is everything.  Depending on the format, my self-motivation will rise or plummet exponentially.

Fine, I understand that you often can’t convey a huge depth of information in those pop non-fiction sources. But when it comes to getting technical, I’d much rather watch a nice video tutorial for an hour than read two pages of written instruction.

Last week, I began a language called “jq” which may or may not be an acronym (and no, it’s not JQuery).  So, I was stuck with a huge manual consisting of a list of functions and examples of each function.  My mentor chose it on purpose because there’s very little “google support” for this language (as in, you can’t just google your problems, you figure them out on your own). No more badges from Code Academy, no more “energy points” from Khan Academy and no more multiple choice quizzes from Coursera.  I’m was on my own.

Here are the thoughts I had while embarking on this endeavor:

  1. *Opens manual and scrolls down* Hmmm, this doesn’t look too long
  2.  I can take a few minutes to go on facebook because obviously the manual will take me no time at all to read
  3. *10 minutes later*  I’m ready! Let’s look at the first line: “A jq program is a “filter”: it takes an input, and produces an output. There are a lot of builtin filters for extracting a particular field of an object, or converting a number to a string, or various other standard tasks.”
  4. Yep, I totally got this.
  5. *A few lines later* “This option reads all the JSON texts in the named file and binds an array of the parsed JSON values to the given global variable. If you run jq with --argfile foo bar, then $foo is available in the program and has an array whose elements correspond to the texts in the file named bar.”
  6. …………..
  7. Maybe I’ll just take a little break and go on facebook again.
  8. Ok, back to work.
  9. Maybe I’ll skip that line for now. I’m sure I won’t need that function later.
  10. This line doesn’t look great either.
  11. Oh man, this is boring.
  12. Snack time!!
  13. I think since I’m eating, I can read some Game of Thrones.
  14. Ok, back to business. Oh man. I don’t get this at all.
  15. I think I’ll just look at some posts on my Reader.
  16. *Some time later*
  17. Ready for another crack at it.  Let’s do this.
  18. Hey, I actually understand this one!  Let me try implementing it!
  19. Nope, nope, I definitely didn’t understand it.
  20. Let’s try reading it again.
  21. Wow, this is really hard to concentrate on.
  22. I don’t get it again.
  23. Maybe another break?
  24. No. No. I’ve got this.
  25. Maybe another snack to boost my energy.
  26. *Repeat 1-25 a couple of times.*
  27. *Try another 30 implementations of that one line of code*
  28. It’s a miracle, it works, it works, it works!!!!

And that’s how I spent an entire day writing one damn line of code.  Seriously.  One line.  I was so freaking proud of myself by the time it actually did what I wanted it to do.

The good thing that came out of this one “strenuous” day is that after it, I was actually able to use the language (minimally).  For me, it’s all about vaulting that initial barrier to entry.  Once that’s over, I love knowing that I understand enough to actually do something.

But those manuals…oh man. I’d appreciate any tricks or tips you have to get through such unpleasant tasks!

 

Title image from girlsgonestrong.com.  And no, that is not me, but I’m pretty sure I can make that expression too.

 

 

Advertisements

One thought on “28 thoughts everyone* has when learning to code via a manual.

  1. codeinfig says:

    learning to code from a manual is like learning to speak from a dictionary. its just not what its for. if the language is really simple and only has a hundred words or less, maybe you can learn it easily enough from a manual. even then…

    as for video tutorials, theyre fantastic. even when im just reviewing, i can watch video tutorials for much, much longer than i can make it through written ones.

    a tutorial teaches you concepts, and a manual is best for fleshing out (or even just having a comprehensive list of) finer details. but just like the best way to learn a spoken language is to go where its spoken, the best way to learn a computer language is to find stuff thats easy to take apart.

    at least it used to be. if video tutorials work, definitely use the video tutorials. save the manual for looking things up later. 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s