Xp

(redirected from Pair programming)
Also found in: Dictionary, Thesaurus, Encyclopedia, Wikipedia.

XP

abbreviation for xeroderma pigmentosum.

Xp

The X chromosome that a daughter receives from her father.

xanthoma palpebrarum

; XP soft, yellowish plaques of fatty tissue; patients with hypercholesterolaemia may develop XP of eyelids
References in periodicals archive ?
Empowering teachers to create educational software: A Constructivist approach utilizing Etoys, pair programming and cognitive apprenticeship.
During the pair programming sessions, teaching assistants--who had been specifically instructed to provide suggestions that scaffold learning instead of "model solutions"--would go around the classroom to answer questions.
As a teaching-learning strategy, pair programming is grounded in the principles of collaborative learning methods, aimed at interaction between learners in the discussion and solving of problems (Ferzli, Wiebe, & Williams, 2002).
Pair programming enables the company to avoid situations where only one person is familiar with the code of some module.
The impact of pair programming on student performance,perception and persistence.
17) Pair programming (PP) allows for guidance and constant review of keyed data by the navigator to identify errors, and it provides a structure for peer support through collaborative learning.
However, most programmers are long conditioned to working alone and often resist the transition to pair programming.
Studies have showed that students taught with pair programming (PP) often perform better in CT than with solo programming (Lye & Koh, 2014; Werner & Denning, 2009; Werner, Denner, Campe, & Kawamoto, 2012).
LaunchCode partners with companies like Engage who agree to pair a new coder with an experienced developer using a pair programming model.
Increased retention of early computer science and software engineering students using pair programming.
The twelve practices of XP are as follows: the planning game, small releases, system metaphor, simple design, continuous testing, refactoring, pair programming, collective code ownership, continuous integration, 40-hour work week, on-site customer, coding standards.