“How do you know when you’ve learned something?", my senior colleague asks me.
After a year in my job of helping people learn, I still haven’t thought enough about this question — and I know it. But I hate hate hate letting on about this fact, so I think for a minute or two (a feature of our company is that we always take as much thinking time as we need) and then I say:
- A weekly newsletter of new work, links, and other bits and pieces.
- Gary's Lament
- An an RPG based on things that happen and people I meet.
- Soft Wet
- Live essays on arcane and ancient software.
- My slightly weird twitter feed.
- This blog
- Scroll down…
Imagine your job is to find out what code does and how it does it. How do you go about it? You will undoubtedly draw on vast reserves of knowledge, experience, strategies and rules of thumb. Eventually, by an awe-inspiringly complex orchestration of activities, you will come to an explanation.