When the tools get in the way

Back in the day, computers were fairly stripped down.  To interact with them, you used the command line.  To code, you used a text editor that didn’t look that different from the command line (emacs, pico, vi).  Even when gui interfaces came along, to make web sites, you often just popped open a text editor (which always functioned as a plain text editor) and then uploaded your files through an FTP client or through the command line (which did more often than not).   Many great tools came along that somewhat simplified this process, but some also hid this process, so that if you used, say, a wysiwig html editor, you really didn’t understand that when you saved a file, you were also uploading it.

Nowadays, people don’t edit straight html that much (outside of some professional environments).  Now, they type in boxes (as I’m doing now).  If you want to teach writing straight HTML, the tools are sort of working against you.  TextEdit on the Mac requires setting it to plain text to make it HTML safe, but even it chokes a little on things like apostrophes.  Other text editors do a good job, but then one must use an FTP client or command line, which is probably fine if you’re working with, say, 17-20 year olds, but is painful if you’re working with 13 year olds.

We’ve made a text editor plus FTP client work, but still, every class period, we run into some difficulty.  We’ve overwritten things here or there and all kinds of other things, so I’m switching to an browser-based editor that hides some of the FTP stuff.  You have to put in the information initially, but after that, it’s saved and assumes that’s the site you’re always working with.  The editor will work with several languages, which will be helpful as we begin to work with some javascript later.  Also, it shows the file structure, so that students can visually see where they are.  That should be helpful going forward as well, as we need to create folders, etc.

Teaching at this level means really thinking about the tools you’re using and whether or not they’re getting in the way of learning the things you’re really teaching.  At the college level, maybe you start out with the “tools of the trade”, but at younger levels, starting with Eclipse or IDLE can lead to frustration before students have even begun writing a line of code.  We’re not teaching software engineering after all.  We’re teaching students how computers work, and how we can make them do cool things for us with just, as one of my students put it, “some random letters and stuff.”   I’ve thrown my high school students into command line stuff and for some of them it’s mind blowing and painful.  Which is why I’ll switch to something that’s much more straightforward and closer to how they already use their computers.  I do want students to understand the innards of computers, but I don’t want them to be frustrated by it.  I want them to be fascinated by it.  So we’ll use tools that are easy while exposing some of what those tools hide.

4 Replies to “When the tools get in the way”

  1. The foundational understanding of HTML, CSS, JS may or may not be critical for all people, but it comes in handy on a regular basis even when using WYISWYG interfaces (I always edit WordPress in text mode, but I love code).

    Or how few people really can diagnose issues or learn simply via View Source?

    There are gobs of great web best editors that show the results of code side by side, test before deploy -e..g http://jsfiddle.net/ but there are so many I can even get to them.

    Or Mozilla’s Thimble, a great way to remix other people’s code, and modify, see results in real time.

    Or Code Anywhere where you even get a virtual server
    https://codeanywhere.com/

    It might be a challenge with more tools than none 😉

  2. Bob, I’m using ShiftEdit, which works pretty well so far. I’ve looked at codeanywhere that Alan mentioned, but it looked too hard for Middle School. I’ve used Thimble as well, but since I’m having them create their own site, it works for learning the HTML/CSS, but not for solid site creation.

  3. All those are good suggestions. I’ve used some of them for different purposes. I guess my challenge was how to do what I need to do–create and edit live web files that live in a particular place–without confusing the students too much, but not hiding anything too much either. Another issue we have to deal with is the whole working with children thing, some under 13, so I have to find sites that don’t gather personal information. I used ShiftEdit because they can log in with their GAFE login.

Comments are closed.