A Brief Bio...




An accomplished, forward thinking and conscientious leader of learning with a zest for technology both in my personal and professional life. Continually seeking new and inventive ideas to teach,share and inspire others with is a committed goal of mine. A hobby that is my profession draws reassurance from colleagues and students alike that theirlearning and technological requests are my sole priority. With this background, I am dedicated to enthusiastic and innovative teaching as a means of creating a lifelong love of technology forchildren. Experience



Learning Ethos

Creativity in the curriculum is the backbone to a great experience in the classroom- it has to be the central element to it all otherwise there’s little enjoyment for all involved.

When students realise that there is as much fun gained from your side of the classroom as theirs, then the love for the learning involved is there from the get go – even if the lesson in hand goes awry - the kids [and the staff in your classroom at the time] know that you had their interests at heart.

Show that you learn alongside everyone else, that enthusiasm for the subject is evident and all else will fall into place...

Experimental Learning - Practical Outcomes

Taking a leaf from the Google (or HP or 3M depending in your sources) policy of experimental approaches to the cause in hand, I prefer to work on the 80-20 principle. This varies of course and in realistic terms is more like 90-10/ 18-15 depending on whole-school commitments. However, this principle has been a staple since my first post with a consistent budget attached to it.

The percentages are a rough guide and are applied to expenditure too. Why do this? The wins outweigh the losses almost every time. Take the proscribed Computer Science/ Computing curriculum as a whole. In it's raw form at the current state is relatively dull. The creative side has been whittled from it and the expectation is for regular teachers to stump up the opportunities for learning based on a few Sunday's/ late Wednesday night (whichever fits into your personal life and staff cohort best) planning meeting and produce exemplary practice.

How can you be expected to be allowed (and lauded) to fail if you don't have the resources/ time/ money to be able to experiment in a field that changes almost hourly? Quite how did Gmail materialise again? How do you expect your team to develop new skills (even through secondary and tertiary learning) while beavering away on a project?

Therefore, I plan both the calendar and our budget to reflect this. It's an imperative part of being in the Tech team. 

It's fun too. :)