![]() |
| Courtesy Stuart Miles. FreeDigitalPhotos. |
Don't be too impressed. All I've done so far is teach myself the basics of HTML. I can create headings, new paragraphs, and, if I'm really lucky, add an image to text.
That said, trying out a wholly new skill has taught me some things about what makes learning fun. I may be taking baby steps, but every step is a celebration for me. And that's got me wondering, What is it about the way one learns to code that makes it fun, and how can I duplicate this experience in the English classroom?
Here's what I've concluded is important:
Clear, easy-to-follow models. When I'm adding code to my text editor, I'm usually closely following the sample code in the tutorial. If I want to add a link to my code, I look up the tutorial section on links, then make my code look like the tutorial's code. If I want to add an image, same thing. HTML is at least straightforward, since there's no doubt what the code should look like.
Students depend on models for positive learning experiences. If they're going to produce something, whether it be HTML code or a reflective essay, they need to have some sense of what the final product turns out looking like. While I'm not always able to provide the exact models my students need (I cannot provide a model for a summary my students are writing on a particular essay, for instance, lest I give away the answer!), the more models I can provide, the better my students will perform, and the happier they will be.
Discrete, easy-to-master tasks. One thing I've noticed about learning HTML is that I don't have to learn everything all at once. Rather, I learn things just a little bit at a time. I learned first to add a paragraph. Then I learned to add emphasis to text. Then I learned to write a table. I'm still working on adding images and links to text, but that's okay, because meanwhile, I've learned to change the link color. I'm accomplishing one thing, even if I haven't figured out everything yet.
Especially with something like writing, when many things happen at once and not always in the same order (for instance, drafting and research are not always completely finished before revision begins!), it can be difficult to break the holistic task of writing a paper down into smaller tasks, but insofar as this is possible, it needs to happen. Students need to be asked not to write an essay but to add a quotation, or even better to add a block quotation and then to add a paraphrase; the hope is that even if they haven't altogether figured out block quotations, they can pat themselves on the back for figuring out paraphrase, and feel as though they're making progress in the larger task of mastering essay writing.
Visible results. When I practice HTML, I practice on a document created through my computer's text editor; this document is saved as an .html file and can be opened in a web browser. I make a change to the document, refresh the web browser, and immediately I see the results of whatever changes I've made. This makes me feel as though I'm accomplishing something. I may not be able to do much in HTML, but when words show up in Google Chrome and links change colour because of code I added to my document, I feel very skilled!
Students need to feel equally accomplished when they write something. They need their writing to have immediate, observable, real-world results. This can be difficult to achieve in the English Composition classroom, since I am nearly always the only one who reads student papers. (I am aware that some colleges manage to publish student work - say, as a collection of English papers, and while this is a step in the right direction, because students are unaware of who reads their papers, observable results are still limited.)
Yet one way that I can supply real-world results is by leaving feedback which comments not only on students' writing skills but also on the way their writing affects my thought. If they a particularly apt quotation makes me think, I should say that. If their introduction really grabs my attention, I should say that. The other way to supply visible results is within the classroom itself. When we learn a new skill, the learning opportunity should be crafted so that students can clearly see what they are accomplishing through learning. If they can walk away from class with something they created, even if it's as small as a single Works Cited entry that they know they are correct, they will have evidence of their learning. Having something you've created through the learning experience is an excellent, visible way to make learning fun.
Ample, clear feedback. The other benefit of having immediately obvious results when I am learning HTML is that I know when I've got something wrong, and when I've got something right. When my heading shows up as ordinary text, which happened last night, I know without a shadow of a doubt that I've made a mistake in my code. I can also go back through the code, find the error, correct it, and when I reload the page, know without a shadow of a doubt that my code is correct.
Having sufficient feedback is actually the one place where I would say teaching myself HTML is lacking, since when I get something wrong, and then wrong again, and still wrong, it's clear to me that I have something wrong, but I don't always know how to correct the problem. For instance, I haven't altogether figured out how to add links to my HTML code; I can link to tutorial websites such as HTML Dog and W3Schools, but not to Google. I'm not sure why; I think it has something to do with the sites themselves, but without someone to ask, I can't be sure.
Students need plenty of feedback. They need to know, as soon as possible and as specifically as possible, when they've made an error, they need to be able to locate the specific error, and they need to have coaching to correct that error. If they are left to flounder on their own, without knowing whether they're headed in the right direction or not, their work will suffer.
Mistakes are okay. In writing the previous section, I decided to test out my skills in adding links via HTML. I switched the blog from "Compose" to "HTML" and added the code which I thought would make the words "HTML Dog" a link to www.htmldog.com.
Here's what I got:
and
Students need plenty of feedback. They need to know, as soon as possible and as specifically as possible, when they've made an error, they need to be able to locate the specific error, and they need to have coaching to correct that error. If they are left to flounder on their own, without knowing whether they're headed in the right direction or not, their work will suffer.
Mistakes are okay. In writing the previous section, I decided to test out my skills in adding links via HTML. I switched the blog from "Compose" to "HTML" and added the code which I thought would make the words "HTML Dog" a link to www.htmldog.com.
Here's what I got:
and
If you click on that word "and", it will take you to HTML Dog. In other words, I added the link, but I got the display text wrong, somehow. My reaction was to celebrating adding the link. Who cares that the word displayed is "and"? Eventually I'll figure out how to get the display text correct, but adding links is one of the more difficult parts of HTML for me, and I'm thrilled that I added any link whatsoever without looking at a tutorial.
Students will make a lot of mistakes when they write a paper. This is natural: A well-written research paper is an incredibly complex thing, demanding multiple academic and critical moves to come off without a hitch. While, as a teacher, I do need to clearly point out students' errors so they can correct them, it's really important not to let the pointing out of errors take over the experience. Every step forward, every sign of progress, even if it's only partial progress or a little bit of progress, is worth celebrating. If we waited for everything to be perfect before we started celebrating, we'd be waiting a long time.
To conclude, the last thing I've learned is that to be a good teacher, it's important to be a learner as well. Learning something so completely new for me has given me an insight into the learning process, which I haven't had for a long while. It takes humility to become a student again, but the narrow and difficult way is the way that leads to abundance, and this holds as true in the classroom as it does in our spiritual lives.
Students will make a lot of mistakes when they write a paper. This is natural: A well-written research paper is an incredibly complex thing, demanding multiple academic and critical moves to come off without a hitch. While, as a teacher, I do need to clearly point out students' errors so they can correct them, it's really important not to let the pointing out of errors take over the experience. Every step forward, every sign of progress, even if it's only partial progress or a little bit of progress, is worth celebrating. If we waited for everything to be perfect before we started celebrating, we'd be waiting a long time.
To conclude, the last thing I've learned is that to be a good teacher, it's important to be a learner as well. Learning something so completely new for me has given me an insight into the learning process, which I haven't had for a long while. It takes humility to become a student again, but the narrow and difficult way is the way that leads to abundance, and this holds as true in the classroom as it does in our spiritual lives.








