Book Learning; was:Re: [agile-usability] Apprentiship and first person learning
- (responding to Jeff)Sorry I'm late, just catching up on my mail backlog...Saw this and just had to jump in.
believe> That experience changed the way I read books. I now
in> there's something important every author can't get across
practice.> their text - something important about the /way/ they
time> So, while I read the books, it's critical for me to find face
them> with these thinkers to watch them work, hear some anecdotal> stories, and really understand what's important toStrongly agreed.I recall the first time I started reading 'agile' writings. I was doingquite well fitting in what was said to my current world view, andas a result just not 'getting' what the author was really saying.Then I started getting worried by the number of 'loose end'disconnects. I began to suspect that maybe I needed to changemy world view (having needed to do that several times before,I spotted the symptoms).In this case, I thought a bit about what the author might mean,and began to realise that it fitted very well with the way I'dbeen developing software for the 7 years before I got inductedinto the Rigorous Software Methodology way of thinking.What the agile approach was doing was adding rigour to theway I used to work.What books can't do for you very easily is change your worldview. One has a natural tendency to fit any new ideas into anexisting world view, and it's hard to change world view withoutsome degree of interaction with a person that holds the newworld view.Paul Oldfield