Reflecting on learning?
• Defined and object model
• Specified what you want it to do
• Defined events
• Designed functionality
• Talked in pseudo code – if this then that and so on.
Great fun!
We thought it might be useful (at the same time as knowing it is an impossible task at another level) to try and reflect on how I made this shift in thinking. It is hard to do this without sounding too grand or grandiose – so apologies in advance (just take it down a notch when you read it yishay).
Serendipity and learning
The process of learning how to between my abstract ideas and how these might be thought of in programming terms was aided by my turning up at Yishay’s without having emailed him my attempts at the assignment. That is we could not get tangled up in the technology, in the programming problems I was having. Instead I ended up thinking about what I was trying to do. This highlights for me the way in which learning demands different levels of thinking and how different technologies help or hinder or position a person to what it is that they are trying to do (mean or think). If I had remembered my flash stick would probably still be trying to make a div box (which obviously I will now have to do).
Experiencing the spatial logic of the coding
I think spending considerable time staring at source code of various websites, and trying to make the link between the visual interface and the code helped me begin to engage (all be it still in an incredibly basic way) with the ways in which coding represents the spatiality of a page, and with the ‘look’ the grammar of a page of code.
The knowledge I needed to understand and solve the problem
Looking at the source code of pages and moving iteratively between the design and the code, and just looking at different pages and the differences in code was useful in that it gave me some ways to think about how I could describe what it is I want to make – to begin to solve the problem of how to imagine and make concrete my idea. So partly with out a language of any kind that reflects the primary concerns of what programming is I could not really get there.
‘Your thinking like a programmer’
Well I wish I truly was able to think like a programmer, but maybe this is a start, and in relation to learning I think this is key. Beginning to attempt some of the practices of a programmer – through talking to Yishay (and Gordon and Chand) I have kind of wanted to talk that talk and enter that world of practices:
• In expressing my interest in the area at where I work
• Adopting, using, trying out and finding out some programming language: literally html and java, but also listening to ‘how programmers about programming’
• Reading some stuff on programming
• Staring at sites in view source
• I have in a very minor way learnt something of what that might mean. Perhaps more than that I have just understood that programming is a form of representation, that it demands a stance or viewing position on the world, that it has concerns that shape and position the ‘identity’ of the meaning maker.
So tomorrow I will buy my html ref book and go back to try the techy stuff.


