Jennitta Andrea has published a wonderful experience report in http://www.stickyminds.com/BetterSoftware called The Case of the Missing Fingerprint.
Well worth reading. Nice work.
I attended a fabulous session at XTC on Neuro Linguistic Programming (NLP) given by Rixt Wiersma. Obviously we could only touch on a small area of NLP in the time available, but it inspired me to want to re-read my NLP books – and that’s always a good thing!
We discussed Robert Dilts’ model of thinking about personal change, learning and communication. Learning, change and communication can take place on different levels. Basically we do not change in bits and pieces, but organically, from one level to the next. To be effective you have to communicate on the same level as the other person. The levels are:
The take-home point for me is that in order to have effective communication with someone you need to form a rapport and respect his or her internal models (ie the best rapport comes when you communicate on the same level). Obvious really, but you have to be told these things sometimes!
One very scary quote (think it was Richard Bandler):
To find out the beliefs and values of a software developer look at their code
Just finished reading “Built To Last” by Collins and Porras - a wonderfully thought provoking study of what makes truly great companies.
Something that interested me is that, while they plan and have clear goals, they are also evolutionary and constantly adapting and changing. One point that they ram home is that visonanry companies create discomfort - to oblitorate complacency - and thereby stimulate change and improvement before the external world demands it.
They also have this wonderful parable of a martial artist kneeling before he master sensei to recieve their hard-earned black belt.
“Before granting the belt, you must pass one more test,” says the sensei.
“I am ready,” responds the student, expecting perhaps one final round of questioning.
“You must answer the essential question: What is the true meaning of the black belt?”
“The end of my journey,” says the student. “A well-deserved reward for all my hard work.”
The sensei waits for more. Clearly, he is not satisfied. Finally, the sensei speaks. “You are not yet ready for the black belt. Return in one year.”A year later, the student kneels again in front of the sensei.
“What is the true meaning of the black belt?” asks the sensei.
“A symbol of distinction and highest achievement in our art,” says the student.
The sensei says nothing for many minutes, waiting. Clearly, he is not satisfied. Finally, he speaks. “You are still not ready for the black belt. Return in one year.”A year later, the student kneels once again in front of the sensei. Once again, the sensei asks: “What is the true meaning of the black belt?”
“The black belt represents the beginning – the start of a never ending journey of discipline, work, and the pursuit of an ever-higher standard,” says the student.
“Yes. You are now ready to receive the black belt and begin your work.”
I buy that story.
There is lots of talk in the Agile community of the parallels with Manufacturing.
Mary Poppendieck (Lean Software Development) points out that development is an exercise in discovery, while production is an exercise in reducing variation, and for this reason a lean approach to development results in practices that are quite different than lean production practices.
That’s not to say that we cannot learn from Manufacturing - certainly the drive to reduce waste (muda as its called in Lean Thinking). reducing batch sizes and focusing on quality are equally applicable to software. I just liked Mary’s overview.
Oh well, back to the book…
I would normally ignore books with a title like Java Open Source Programming: With XDoclet, JUnit, WebWork, Hibernate (Java Open Source Library) - but this one is different.
For me the best thing about this book is that it shows you how experienced developers produce a well crafted, easy to test, web application. It walks you through using interfaces to separate the database from the code. It provides oooodles of examples of using mock objects to make testing easier. It shows how experts use Test Driven Development (TDD) on a real world (web) application.
Oh, and it uses some nice open source libraries along the way. One of the best ways to learn something new is to pair with an expert. The next best thing is to read a book like this!
Shame about the title!
