Part 3. Maintainability
After a month, the Klafim project enters what Alabatross calls the maintenance phase. Small new features need to be added on a weekly basis. Bugs need to be fixed; nothing dramatic... .
Monica, Theo’s boss, decides to allocate Dave to the maintenance of the Klafim project. It makes sense. Over the last few months, Dave has demonstrated a great attitude of curiosity and interest, and he has solid programming skills. Theo sets up a meeting with Joe and Dave, hoping that Joe will be willing to teach DOP to Dave so that he can continue to advance the good work he’s already done on Klafim. Theo and Dave place a conference call to Joe.
THEO Hi, Joe. Will you have time over the next few weeks to teach Dave the principles of DOP?
DAVE Why? Is it because I don’t have enough experience in software development? I can guarantee you that I’m a fast learner.
JOE It has nothing to do with your experience, Dave.
JOE Theo, I think that you could be a great mentor for Dave.
THEO But, I don’t even know all the parts of DOP!
DAVE Come on! No false modesty between us, my friend.
JOE Knowledge is never complete. As the great Socrates used to say, “The more I know, the more I realize I know nothing.” I’m confident you will be able to learn the missing parts by yourself and maybe even invent some.
THEO How will I be able to invent missing parts?
JOE You see, DOP is such a simple paradigm that it’s fertile material for innovation. Part of the material I taught you I learned from others, and part of it was an invention of mine. If you keep practicing DOP, I’m quite sure you, too, will come up with some inventions of your own.
THEO What do you say Dave? Are you willing to learn DOP from me?
THEO Joe, will you be continue to be available if we need your help from time to time?