Nazis, Not Pirates

I was cleaning up my home office recently and I found a couple of installation disks for Apple’s OS X Tiger operating system, 10.4.7. They must have come with the Macbook Pro I bought back in early 2006, and since that time I’ve upgraded  several times, to 10.5 (Leopard), 10.6 (Snow Leopard), 10.7 (Lion), and in the not too distant future I’m sure I’ll make the move to 10.8 (Mountain Lion).

Because I have absolutely no need to keep the OSX Tiger disks, I figured I’d sell them on eBay. After all, they might be of some use to someone with an older Mac who wants to stay on that older version of the OS, who possibly has lost or damaged their original disks. I listed them online for $1, eBay’s minimum bid, and hoped that they  might be of some benefit to someone, somewhere.

Less than 24 hours after listing them, I get an email from eBay telling me they had to pull the ad after getting a takedown notice from the Business Software Alliance. “Your item was removed because of a request we received from BSA asking us to remove the item”. They say that “software offered for sale is in violation of an enforceable license agreement, which constitutes a copyright infringement”.

WTF? Are they serious? This is an operating system that is nearly 5 generations old and is no longer for sale.  The only people interested in this software would already own the Mac hardware to run it on, which means they did, at least at one point, own their own copy of the disks anyway.

The email suggested I should write to the BSA if I had further questions.  So I did…

Dear BSA,

I got the following email from eBay after I listed a set of Mac OSX 10.4.7 installation disks…

You guys cannot be serious?

This is a legacy operating system, no longer supported by Apple. How can it possibly be seen as a copyright infringement?  What damages can the BSA possibly claim?  This is not taking sales of new software away from Apple, nor depriving Apple of income.  The disks are sitting in my drawer gathering dust, and I listed them for the absolute minimum price allowed ($1) in the hope that someone who needs them, running an older Mac, might benefit from them.

Surely you understand that these disks are of no benefit to anyone who does not already own the hardware capable of running the software?  By implication, they have already bought – and probably subsequently lost – the disks that came with their original system.  All I’m doing is offering them to chance to get a genuine copy of the disks they have already bought.

Unlike the Windows operating system, Mac OSX cannot be bought as a standalone product, and so whoever has hardware capable of running OSX 10.4.7 has already bought the software, since it came with their hardware! If those original disks have been damaged or lost, the disks I was offering on eBay will simply allow them to have a genuine replacement for something they have already paid for.

Please reply to this email and explain the rationale behind your request to pull these disks from sale on eBay, and also please explain to me – realistically – what damages are being done and to whom.

I await your reply.

Those who know me well would know that I usually do my best to do the right thing regarding copyright, but this seems just stupid to me. Copyright is supposed to protect people from loss of income due to the theft of intellectual property. I fail to see how this takedown notice does that. Thanks to the nazis at the BSA, somebody who might get some benefit from owning the disks for this 6 year old operating system will no longer be able to, and I’ll be deprived of a whole dollar.

Meanwhile Apple still have over $100,000,000,000 in the bank.

Victimless crime? Copyright gone mad? Or am I just being unreasonable?

The Software Conundrum

Many people I know struggle with technology. They bumble by, more-or-less managing to make their computer do what they want it to do, but often without that real sense of confidence that comes from feeling fluent with the software they are interacting with.  And let’s face it, when we talk about “technology”, we mostly mean “software”. Sure, there are some hard-to-use hardware devices but by and large when I watch someone struggling to feel comfortable using “technology”, it’s usually because they are out of their depth with the software they are trying to use, not the hardware.

It might not seem like it when you’re so frustrated you just want to throw your laptop out the nearest window, but companies who build software try really hard to make their tools easy to use. Of course, not all software is actually easy to use, but I do believe that all software designers really do try to make their software as easy to use as possible. It’s not easy… some of the things we expect software to do are incredibly complex, and designing software that does complex stuff while also making it easy to use, is really hard to do well!  But the next time you are struggling to use a piece of software, remind yourself that someone, somewhere, probably spent a great deal of time and energy trying to make it as easy as they could. And no matter how much it might feel like it, the software designer’s goal was not to confuse and frustrate you.

Because writing software is so hard, it takes a special kind of person to do it. Software developers are usually incredibly intelligent people because you really do need to be fairly smart to write software. Most developers also have very systematic and methodical minds, because, again, that’s just the sort of mind you need to write software. It’s this combination of high intelligence and methodical thinking we sometimes call an “engineer’s mindset”, and while you need it to write good software, it’s really not the way the majority of us think.

And that’s part of the problem of why there is so much “hard to use” software. The people who create it are often on a completely different planet to the people who use it.  For a super smart software engineer, the term “easy to use” might mean something entirely different.  Because most “dumb users” find it difficult to think the way engineers think, and many engineers are unable to put themselves in the shoes of the average end user, there is often a huge mismatch between the two groups that ends up making software seem much harder to use than it should be. (You might like to read The Inmates are Running the Asylum by Alan Cooper for a really good insight into this problem) Thankfully, software has gotten much, much better over the last few years thanks to much better development environments and more flexible programming frameworks, a greater emphasis on end-user usability testing, a greater acceptance of the idea of a “public beta”, and also the “appification” of complicated software in small, app-sized chunks on easy to use mobile devices.

So thankfully, things are improving.  But if software is getting better, and companies really DO try hard to make their software as easy to learn and use as possible, why do so many people still seem to find it so damn hard to use?

So here’s a few tips for becoming a much better, more confident and more fluent user of modern desktop software…

Mix it up!

This was one of the most powerful things I ever did to become a more fluent software user… I deliberately started using software that was different to what I was used to. If you use a software tool to do a particular task, find out what other software tools do a similar thing, and try them.

For example, if all your word processing is done in Microsoft Word, try using some other word processing tools for a change. Libre Office Writer, Google Docs, Zoho Writer, WriteRoom, Scrivener, AbiWord… the list is long if you look. There is something incredibly liberating about trying a different tool than the one you’re used to. It forces you to see things more conceptually – to understand the concepts of formatting text, rather than simply remembering where the Bold button is located. As you move between multiple tools that do the same task, you start to see the commonalities and the differences between them.

You realise that all tools in this category have certain core features, but you also see how different tools implement some of those features better or worse than others. You start to think in terms of function rather than form. You develop a better ability to scan your eyes over the interface quickly, spotting the buttons you recognise, even though they might look a little different.  You realise that the design of software is far more consistent and predictable than you maybe imagined it was. You start to see the ways that different programs handle the same common file formats.

Are you a PowerPoint user? Why not try Keynote, Google Presentations, SlideRocket, Libre Office Impress, Prezi or 280 Slides?

What do you use to edit video? Whatever you use now, take a look through some of the alternatives from iMovie, Windows Live MovieMaker, Pinnacle Studio, Sony Vegas, Adobe Premiere Pro or Premiere Elements, Final Cut Pro X.  As you might imagine, if you actually did try all these different video editing tools, you wouldn’t just know how to use a bunch of video editing tools, you would truly understand the core idea of what it means to edit video.

There is great alternative software in most of the major categories. Just go to Google and search for [alternatives to X] where X is the software you use now, and see what you can find. Much of it is free to try, if not completely free to use.  Using lots of different software tools that do more-or-less the same job makes you a far more flexible and adaptable user. You don’t have to permanently switch from your old faithful tool if you don’t want to (although you might be surprised at how good some of the others are!) Switching to a new tool is not the point of the exercise. But by trying lots of new tools you will develop a far deeper understanding of what software is all about, and your technological fluency will take a supercharged leap forward.

Trust me on this.

Check out your options

Whenever you work with a new piece of software, take a moment to explore the options or preferences.  On most Windows software you’ll find it under the Tools > Options menu, and on the Mac its in the application menu under Preferences.

Whenever I get my hands on a new piece of software, I go straight to the prefs or options and spend a few minutes looking through them. Those few minutes are always paid back in greater productivity through having a better sense of what the software is all about, plus I can usually find lots of little tweaks that make the software work the way i want it to work.

It astounds me how often I see people struggling (sometimes for years!) with some annoying behaviour in their software that can be easily changed simply by unticking a checkbox in the preferences. Don’t be one of those people.

What’s on the menu?

The other thing I will always do with any new piece of software is just take a moment to look through all the dropdown menus to see what’s there. Many of them will be immediately recognisable – obvious ones like cut, copy, paste, select all, etc – through to those that will give you some clues as to what the software might be able to do.

Seeing choices like Arrange, Group, Align, etc immediately tell you things about what the software can do.  The View menu often lets you change the way you see the software by accessing fullscreen mode, changing zoom levels, and so on. If you’re observant you can also pick up some great keyboard shortcuts as well.

Look for menu items than you don’t recognise too. For example, if you’re usually an Internet Explorer user you might be intrigued by options such as Chrome’s Incognito Window. Click it. See what it does. It’s software, you can’t really break it, so go explore!

Don’t be afraid to call for help

Every piece of software I’ve ever used has a Help menu. Someone, somewhere, went to a lot of time and trouble to document this software and explain what it does, how to use it, and how to get the best out of it. Why would you not use it?

And yet, whenever I see someone struggling with a piece of software, I can almost guarantee that the answer to “have you checked the Help menu?” is no. C’mon! Just use it… Look it up if you have a problem, or just glance through it to pick up some useful tips. Don’t be so helpless.

I can’t even tell you how many times I’ve showed someone some ridiculously simple time-saving tip that has totally changed the way they work, only to have them ask “How do you find this stuff??!”

Easy. I once got stuck on the exact same problem as you, and I looked in the Help menu to work out how to solve it. Just like you can.

If you really don’t want to use the Help menu (“It’s so complicated!”) then just Google your problem. Just type in something like [how do i merge 2 tracks in audacity]. Believe it or not, you won’t be the first person to ever ask that question. Someone has already solved it. Learn from their experience.

Putting this into action with your students

A task I’ve had my Computing Applications students to do several times now is to create a user manual, either in text or screencast format, for a piece of software they’ve never seen before. It’s not hard to find obscure software tools that most students have never heard of, so pick a few for them to choose from and get them to create a user manual for one of them. Not only do they need to learn a completely new piece of software, they also need to figure out how to clearly explain it’s features in a way that non-users can easily understand. They can’t do that unless they understand it themselves.

They’ll need to learn quickly, communicate clearly, have empathy with end users, and also learn new presentation skills. Try also to get them to run some real usability testing with other people using the training resources they’ve created in order to see how well they have communicated their understanding. Everytime I’ve done this, my students have found it a useful and worthwhile task.

Got any other tips for learning new software quickly? I’d love to hear them.  And if you’re a fluent software user, add a comment and tell us what the “penny dropping” moment was for you, when software started to make sense.

Making Thinking Visible

Yesterday at PLC Sydney we held a whole-staff PD workshop with American educator Mark Church.  Mark is a co-author of the book Making Thinking Visible, as well as a contributor to the Project Zero team. I found myself really resonating with much of what he had to say. I liked the fact that his focus was on really good pedagogy, and although I could see many connections to the sorts of thinking that I find myself constantly exposed to in the edtech world, his message had very little to do with the use of technology. It was really just all about good teaching.

PLC brought Mark out from the US especially for this workshop after members of our senior leadership heard him speak at another event. They were really impressed with his message and felt it was just what our staff needed. I tend to agree. In schools like ours, where we are essentially teaching to a largely compliant, affluent and  literate demographic, it’s doesn’t seem to be too difficult to have our students achieve significant levels of success without teachers needing a big “bag of teaching tricks”. We provide kids with content at a sophisticated level, and they generally perform very well in the traditional ways of measuring school success. Based on our HSC results, we certainly manage to create a disproportionate number of highly successful students, although I certainly don’t always agree with the conventional way we measure that “success”. Mark’s message was that we can do much more to really expose the thinking of our students, to help them develop greater understanding of what they learn and to make the learning more authentic and meaningful. To all of that I certainly found myself in much greater agreement.

The first part of the day was spent on some big picture stuff, ideas about education and the ways in which we build a culture in our schools. Enculturation, or the way we create a culture over time, is a critically important aspect of education and schooling and something I feel quite passionately about so I very much resonated with this part of the discussion. The second half of the day was spent looking at a number of pedagogical ideas – Mark called them “routines” – that provided some terrific examples of ways in which we can be better at what we do. I found the day insightful and refreshing, and felt quite energised by the ideas we covered.

Along with some other members of our staff, I used Twitter (and the hashtag #plcpdday) to capture some of the key ideas and thoughts during the day, and I thought I’d just recap a couple of my more salient tweets here, and expand them beyond Twitter’s sometimes frustrating 140 character limit.

Unless a teacher takes time to understand the culture of students, the students will never care about the culture of the teacher

This idea has always been a big one for me. It’s kind of a rephrase of the old “people don’t care how much you know until they know how much you care” line, but I’ve always found it so incredibly true in schools. It drives me crazy that most educators seem to think that “their stuff” is so intrinsically interesting and valuable that students will just automatically be interested in it. They won’t. Students are people, and people want to feel valued before they will buy into what you want. In every school I’ve been in where there’s tension between teachers and students, it is nearly always because of an overly militant, authoritarian approach that says to kids “just shut up and do it my way”. A highly disciplinary approach might win the battle, but it’s never going to win the war. Respect, care, and dare I say, even love, are the basis of a good relationship between teacher and student, and until there is a good relationship it’s going to be an uphill battle.  I suppose this idea particularly struck a chord with me because it something I’ve also talked about a fair bit elsewhere.

Dispositions are developed through enculturation in thoughtful settings over time. OVER TIME. time to uncrowd our curriculums?

The notion of a learning culture is also something that is central in the way I think about schooling.  Too often we think that we can “teach” kids something by giving them a lesson or two in it, and that’s enough. We run sessions about cyberbullying or plagiarism or creativity or digital citizenship, and we act as though by pouring this information into our students’ heads that we have done our job. “We taught it, so we now expect them to know it”. It’s all nonsense of course. We don’t create enduring dispositions by running a session or two on a particular idea and then ticking it off our todo list as done.  Building a disposition is about creating a culture based on the values of that disposition. And that culture needs to permeate everything. It needs to become part of the way we think, the way we act, the “way we do things around here”.  You don’t teach creativity by running a couple of workshops about it.  You teach it by having the values of creativity become an ingrained part of the way you think. You don’t learn it, you become it.  And the key thing is that it takes time. Lot of time. Lots of repetition, iteration, example-setting. You model the big ideas, all the time, over a period of time.  In a teaching sense, this makes it even more imperative that we find ways to uncrowd our curriculum to make space for  this to happen. We need to create the space to have the time to build worthwhile cultural dispositions.

Focusing on the average in education is like looking at the average of a mountain range. All the peaks and valleys disappear.

We build our education systems for the average student. Too often we pitch to the perceived middle.  Sure, we try to come up with strategies to differentiate, but when it’s all boiled down, the structure of most schools is built on the idea that we can process students in groups of 25+, and that by designing for the needs of the whole group we hope to be able to meet the needs of most of the people within it. And as the mountain metaphor shows so well, if you focus on the average high of a mountain range the peaks and valleys disappear. By catering to the needs of the group, we often fail to meet the needs of the individuals within that group. It hard to do well, but so important that we keep trying to be better at it.

It’s far too easy for kids to have the “right answer” and still have no idea about what they supposedly learned.

As a teacher, how many times have you thought you taught students something, only to realise that they still really don’t get it.  You explained it, demonstrated it, they tried it themselves, the practised it, the seemed to master it… and then when they really needed to demonstrate that knowledge or skill, you realise that they still don’t get it. Or worse, the can demonstrate the skills you want them to have – the can pass the test, do the activity, get the right answer – but you can see that there just isn’t any deep, real understanding there. It can be quite demoralising, but it happens a lot. The idea of Making Thinking Visible is to get to the root causes of misunderstandings so that true understanding can be reached.

Mindset change: what if what I teach today shows up on a test 3 years from now? How would I teach it differently?

I liked this idea. We often teach things to our students on the basis that they will need to pass a test on it at the end of the lesson, or the end of the week, or end of the unit. But what if we taught in ways that presumed the information we taught today would not appear on a test for another three years. Would we do it differently? How? What would we change?

The big picture… What are the residuals of education? What does education leave kids with long after they have finished school?

I guess this is the same kind of idea as the last one, but I liked Mark’s idea about the “residuals of education”. A residual is the stuff you’re left with when everything else is gone. So after the homework is forgotten, after the tests and exams ar done and the reports are handed out, what are we left with? What is the truly important stuff that sticks with kids when the ephemeral nature of “school” has passed? And if what we have left over is not the same stuff that we usually give so much importance to, why do we keep giving that other stuff so much importance in the first place?

Let’s change the language… Let’s stop using the word “work” in our classrooms and start calling it “learning”.

Homework. Classwork. Schoolwork. “Get your work done .” “Where is your work?” “What are you working on?” What if we stopped calling it “work” and started calling it what it’s supposed to be… learning. Better yet, what if we stopped giving kids “work” to do, because so often it’s just pointless busy-work that does little more than just keep them busy. It’s colouring in. It’s making titlepages. It’s making a PowerPoint. It’s doing “research” into things that they already know about. Why do we do that? Why don’t we make more effort to ensure that the precious time we have with our students is spent doing real stuff, real learning? We could start shifting this mindset by at least not referring to what we get kids to do as “work”, and start calling it “learning”. Because we’d soon feel pretty stupid referring to their colouring-in and titlepage-making as “learning”.

Looking at how time gets used in your classroom sends a big message about what you value in your classroom.
How does the environment in which we teach say a lot about what we value about learning?
what does the language and style of communication we use in our classroom say about what we value about learning?
If a classroom is set up with rows of desks all facing the front, what does that say about what we value about learning?

These tweets were all focused on the same core idea… how does what we say is really important manifest itself in what we actually do on a daily basis?  If we say we value teamwork and collaboration but our classroom desks are set up in forward-facing rows, what does that tell us? If we say we want our classrooms to be student-centric places, and the teacher still does most of the talking, what does that tell us? If we say we want independent, self motivated learners, and we still infantilise our students by spoonfeeding them with content, what does that tell us?  If we say we want to meet the needs of every child, but we don’t allow for their choices and preferences and learning styles, what does that tell us? The bottom line is that we need to ensure that our beliefs about what and how we teach are in alignment with what we actually DO every day, or things will always be out of whack.

Routines for building understanding… See-Think-Wonder, Connect-Extend-Challenge, What makes you say that?, 3-2-1 Bridge.

Mark wove many of these techniques (he called them “routines”) into his presentation during the day. You can find a more complete list of these routines on the Visible Thinking website. Some people might just call them common sense or good teaching, but they are still a useful collection of teaching techniques that I will certainly be trying to build into my repertoire of classroom skills. It’s far too easy to fall into familiar patterns of teaching, and I think especially so in a school like ours where, let’s face it, the kids are easy to teach, generally compliant and focused on passing the test.

It’s the questions our students ask, not the answers they give, that really let us see what ideas they are grappling with.

In most schools we seem insanely focused on getting our kids to provide answers. We test them with quizzes and exams. We get them to write factual essays. We ask them to solve math problems using the correct formula. We get them to do science experiments where we already know the end result. We seem to always want our students to be finding “the answer”, and the correct one at that. Instead, maybe we should restructure things a little to allow them to ask more questions. More wondering. More curiosity. If we can know what questions they have, we might have a far better insight into what’s actually going on in their heads. We’d get to see their thinking, to observe their understandings (and their misunderstandings). We would be able to see their thinking. Getting kids to give us “the answer” might seem like the obvious thing to do, but it doesn’t really let us see what they understand.

As I hope you can tell, there was lots of great stuff presented during the day, and most of our staff seemed very receptive and enthusiastic about it all. Something that I’ve felt has been missing at our school for a while now has been this common educational language or direction, and I’m glad to see that we finally seem to have found a focus we can all latch on to as we move forward. It’s really refreshing to have a whole staff focus on a shared pedagogical idea – visible thinking –  and one of the things I would like to see happen is the creation of some Visible Thinking study groups where keen staff members could openly explore some of these ideas with each other, sharing suggestions and best practice, and pushing themselves forward to become even better teachers.

I definitely want to be part of that.