[wrote this as postscript for some studies - following the intuition that the common experience of ICT as web 2.0 may eclipse some crucial understandings of classic IT, water down the content of computer science in schools] :
Sitting on a train, after a day wrestling with a research proposal, an interesting synchronicity unfolds. Passengers cram in; opposite one starts a crossword puzzle. Adjacent, one opens a laptop and starts programming. A few minutes layer another passenger gets on, sits opposite, and starts a sudoku. A moment later the sudoku solver and the programmer recognise each other; obviously know each other a little; but don’t talk for long, and settle back to their tasks. I’ve been glancing at the programming beside me; its in a terminal window and is full of test cases and assertions. I guess it might be a test harness for an electronic board.
After a while I notice the approach the sudoku player is taking, systematically listing, in small script at the top of each cell, the candidate possibilities for each square, identifying the most constrained cells first – then reducing elements out other cells once one is determined. I find myself thinking of procedures I could use to program that - looping through each column, and row, with an array attached to each cell; - maybe with colour if one just wanted to hint at productive cells…. I glance back at the programmers screen –and it suddenly seems like that is exactly what he is programming - he flicks a window and I see its called sudoku.py.
My sudden conjecture is that there might be coworkers, since they did recognise each other … even though the common link of sudoku algorithms seems like improbable work .. so I break the convention of commuting silence and start a conversation. It turns out their common focus is not these little numerical puzzles - they actually did a computer science course some years ago; the manual sudoku solver now works in a bank; as a systems designer; the programmer works for a stockbroker, programming automated trading systems – both are tackling the sudokus for distraction.
We chat, and I talk about this research, and Sherry Turkle’s reservations on today’s notion of IT– around the that fact that 20 years ago many kids programmed computers for fun – we all agree on that - but today kids are more likely to be on MySpace or World of Warcraft. I mention my suspicion that the lack of a 'BASIC' – the simple, pre-installed language we learnt with, might contribute to this. I’m interested in their opinions. The stockbroker programmer indicates, wryly, he is happy with the lack of competition coming through from junior programmers. The sudoko banker rebukes him, and warns that below a critical mass that whole sector of the IT industry will be outsourced to India. Working in a large bank, he sees it already; there are no local programmers below the system designers. He also seems bit conflicted about ICT in schools; since he has fond memories of the control he felt in teaching himself programming language, and spending hours trying to make games, on a Commodore 64; but isn’t sure there is a future in it now. The stockbroker programmer disagrees – loves the technical work and sees it as a good career option for students.
I feel like I should interview these two, incarnations of the concerns I’ve been reading over for two days; early dialogue in an outcome space.. after they leave at the little satellite town, I travel on, feeling I might be on to something - that the historical tensions around how IT is conceived corresponds to real and current issues, and the strength of this little debate tells me the issue goes beyond schools - and the idea of visual schematics to examine the tensions might work.
many in education seem set on cheerleading the '21st century ict' ='web 2.0' =transformation' theme - lots of syrupy youtube videos on that theme - but not everyone agrees, or at least not without reservations about what is missing in that equation. Some have even stepped away from the spin and put it all in historical context. Its quite stabilising to have some sense of the real historical trajectory of educational computing - the popular idea that its all progressed betrays some of the real history.
My little boy likes 'The Incredibles' brand of superheroes, so I know that Pixar film rather too well. There’s a clever intro to the movie, where the super heroes talk about their alter egos. One of them, glib and suave, complains that “superladies, they’re always trying to tell you their secret identity. They think it strengthens the relationship or something. I tell them, I don’t even want to know about yourmild mannered alter ego. You tell me you’re Mega-Ultra-Lightning-Babe, and I’m good. I’m good.”
The story around IT can be a bit like that. I don’t want the story of what its really like. Tell me about the hyper-system, and what it can do when its costume is on, and its having a good day.
The reality of these things is not always so fun. I have a friend who works in procurement for a large multinational company – transacting leases on oil tankers and little things like that. He was recently pulling his hair out as the company was upgrading their super duper finance package, which is a world class, company wide, top of the range product,from version 2 to 3. The result, after endless meetings, change management plans, consultants flying in from the US, is that they now have a world class system that is much harder to use, takes 16 keystrokes to complete tasks that used to take 3, and has many of the shortcut commands in another language.
So here’s a few thoughts.
I knew a school in Melbourne, close to 10 years ago, that developed some pioneering approaches to IT in general - all teachers were asked, and required, to work hard to integrate IT in their classes - and also were progressive with learning in general (they were onto the metacognition, “learning to learn” , habits of mind, middle years sort of approaches early on), as well as new uses of space (open learning spaces, passive supervision of pods etc)
(I was in a Catholic school at the time, which would probably have wished to claim a richer purpose in education, and yet I and others from our school were very impressed with the clarity and focus of this schools purpose and mission – everything seemed to pull in the same direction – and so we ended up, via an ICT project, in some sort of mentoring relationship with the school.)
I remember a one senior staff member saying she had to travel to most of the intentional conferences on teaching and learning, to keep abreast of it all.
They also did some really interesting things with intranet / extranets etc; they were early on the block with publishing student timetables to the network, and student / parent portals to the web.
A couple of their own IT staff developed that, supporting the school's general agenda. Its not so hard with some time and support – I recall hearing them say, at a Navconn conference in 2001, thatthey started in Cold Fusion, a fairlystreamlined web environment, and only moved to ASP once they got some skills under their belt. That is, they were just working with the more accessible and flexible tools of the day; aiming at functionality, not necessarily at the most technically advanced pathways. Rapid application development.
An interesting question arises – how would one scale up some of that intranet / extranet innovation?
To my naïve mind, two approaches seem possible.
(1) encourage other schools to foster the same sort of local skills and development. Given there are really powerful open source apps, and development environments, that streamline the process (one example is Moodle), one could expect schools to have a big jump start on those early developers. Some of those projects use a central repository of modules on the web – so one could harness the innovation across the system, magnify and harness the efforts of those two original developers.
The formal educational system could presumably provide some support in getting platforms established. It could also mandate certain standards on how the data must import / export; such as the flavour of XML that was required to exchange data between, say, timetabling and reporting applications, so that local development produced solutions that could still exchange data with each other. And then let schools plug and play and customise their modules; and tap each others development and ideas, within a framework that still maintained standards on how data was handled, exported, etc.
(For a weak parallel, one could look at edublogger, as an example of education colonisinga common platform, in a way that does leverage an existing open source technology (wordpress) - one that is leaping along with regular enhancements from an active community of supporters, using a standard and yet customisable framework. Edublogger is too limited for this to be a good example, since its more of a training / playground –for example, one can’t even modify the underlying Wordpress plugins or themes. Wordpress MU might be a better example, though it would probably be stretching it a bit to try turn it a large scale content management system for a school - its not designed as an admin tool. Moodle, joomla, dotnetnuke might be better examples – where one could enforce some standards on how the flexible app was used /deployed without killing the range of customisations).
[i guess the risks are that some schools wouldn't be in a position to do much in the way of developing it; and may need a fairly standard version, and access to a local skills to customise it.]
OR (2) – one could attempt to build a big system that packages all that functionality into one bundle, does everything, and distribute to multiple schools from a commercial vendor. Sort of like SAP for schools. (Cases has tried this, i think ,with various web modules).
I think there are a couple of reasons why the former approach is pretty interesting.It could tap some of the willing creativity in schools, and allows schools to fully customise their own applications, in a way that off the shelf seems to find hard to match.
The SAP model – a system that does everything – would seem to run a few risks –in terms such development time; and also that the standardisation might make it hard to customise and match against local needs.
In my untutored observations of these things, if a company had something really good already built, it might work – but it seems pretty tricky. Watching attempts to standardise other software apps in schools, including NSW and Queensland, doesn’t suggest this is going to be easy.
One of the most astute people I know in the field of intuitive learning and software design is Kathy Sierra. (Her crash course in learning theory is great, and thoughts on software features is interesting). She’s made her name with applying these approaches to the teaching and learning of a difficult and traditionally dry area, object orientated programming –and turned the classic textbook genre on its head with the result.
I have some feeling for the two developers in the school story - and the notion of proceeding by magnifying their efforts. I wrote an information system for analytical laboratories, in the early 90s, by extending some common productivity software with scripting. … was an after hours project to start with, for the lab I worked in, then a part time job while I did a Dip Ed; and somewhat to my surprise was installed in 6 labs, and reduced the need for admin staff. It lasted a few years after I left; which is not bad for non updated software. Was replaced few years later with a 'proper' commercial product – which was more secure etc, but was less well received than the inhouse tool. Developing from inside the company, one has the advantage of knowing workflow, paperwork, systems, and where to automate the manual work.
Disclaimer – i no doubt sound clueless, but its not the commerical verus free open source thing that i'm getting at here. Its the question of how to scale up successful innovation; seed it again in local environments, tap the creativity in the system, with some means of exchange and feedback, or deliver it from one standardised centre? - and also the development and flexibility issues in the two approaches .. but this is all just my uninformed reflections; and i'm not 100% sure which side of the cartoon i'm on.