I thought there might be a co-relation between the two.
The comment by TrygveReenskaug quoted above fits nicely with the way I like to think about MVC: * The View is connected to the user's eyes; * the Controller is connected to the user's hands; * and the Model is connected to the user's mind.
Pair Programer One see ( led by PP Two's example) Pair Programmer One do Pair Programmer One hear
How much experience with PP do you have? I ask because, having practiced it for quite some time, I don't see any connection to MVC. MVC is about separation of concerns. You do it if you want to be able to replace the input strategy (for example) without affecting the business rules and the output strategy. PP is about collaboration. You do it because you want the programming partners to inspire each other. There typically *is* *some* division of labor happening in a programming pair, but that isn't he only (or even most important) aspect of it, in my humble opinion.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: May 15, 2002
Originally posted by Ilja Preuss: How much experience with PP do you have?
Some before they called it Pair Programming. Pair Programming would be appropriate in two situations, IMHO - training and exploring alternative solutions/brain storming. Otherwise , it is overkill especially as solutions are documented in the code. Though it would be good for every Programmer to get to grips with the practice by asking to PP when needed. I just thought the simplistic take on MVC would be and make PP easier to adopt if that's all it was. But apparently it isn't. [ March 10, 2004: Message edited by: HS Thomas ]
Joined: Jul 11, 2001
Originally posted by HS Thomas: Some before they called it Pair Programming. Pair Programming would be appropriate in two situations, IMHO - training and exploring alternative solutions/brain storming. Otherwise , it is overkill especially as solutions are documented in the code.
Well, my experience is quite different - namely that it is far from overkill for nearly any development task...
Joined: May 15, 2002
OF course my previous post describes PP without the tools and test-driven development. With, PP is another force altogether. I am sure there is a pattern that fits.
PairProgrammingPattern Known uses: Medical schools have a philosophy of, "See one, do one, teach one." [ March 15, 2004: Message edited by: HS Thomas ]