part three

Part 3: Maintainability

 

Innovation

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, has decided to allocate Dave to the maintenance of the Klafim project. It makes sense: over the last few months, he has demonstrated a great attitude of curiosity and seems to have 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 leverage the good work he’s done on Klafim.

THEO: Will you have time over the next few weeks to teach Dave the principles of DOP?

JOE: Yes but I prefer not to.

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.

THEO: Why not then?

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!

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?