avatarBirat Rai

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

2187

Abstract

ks about the class that will satisfy the test.</li></ul><blockquote id="437f"><p><b>Common Misconceptions in Pair Programming</b></p></blockquote><ul><li>You have to do pair programming if you’re doing an agile process.</li><li>Extreme programming forces you to do Pair-Programming.</li><li>I don’t need to try pairing because I know I won’t like it.</li><li>Pair-programming halves the productivity of developers.</li><li>It’s only worth pairing on complex code, rote code yields no advantage.</li></ul><p id="39a9" type="7">TL;DR Paired programmers are only 15% slower than two independent individual programmers, but produce 15% fewer bugs.</p><p id="a0c3"><a href="https://readmedium.com/97-journey-every-programmer-should-accomplish-a0c53dbbfd47"><i>Go to the series</i></a>.</p><div id="10b2" class="link-block"> <a href="https://readmedium.com/97-journey-every-programmer-should-accomplish-a0c53dbbfd47"> <div> <div> <h2>97 Journey Every Programmer should Accomplish</h2> <div><h3>“A journey of a thousand miles begins with a single step.”</h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*ImU1JEXOUUKMJxBF_OP-_w.png)"></div> </div> </div> </a> </div><p id="d42c">Go to <b>63rd<i> Step</i></b></p><div id="f3ab" class="link-block"> <a href="https://readmedium.com/step-63-own-and-refactor-the-build-steve-berczuk-8d85ba39e146"> <div> <div> <h2>Step 63: Own (and Refactor) the Build~ Steve Berczuk</h2> <div><h3>This is the 63rd Step towards gaining the Programming Enlightenment series. If you didn’t learn the 62nd Step, read it.</h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*jhn4i1qZmZ_usLO5gTc-xA.jpeg)"></div> </div> </div> </a> </div><p id="5f94">Go to the

Options

<a href="https://readmedium.com/step-65-prefer-domain-specific-types-to-primitives-312d2a28ccd2"><b><i>65th Step</i></b></a>.</p><div id="91e9" class="link-block"> <a href="https://readmedium.com/step-65-prefer-domain-specific-types-to-primitives-312d2a28ccd2"> <div> <div> <h2>Step 65: Prefer Domain-Specific Types to Primitives~</h2> <div><h3>This is the 65th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 64th Step, read it.</h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*Wc_htdZOxhcfis5EzwCKpg.gif)"></div> </div> </div> </a> </div><blockquote id="ba78"><p><b>References:</b></p></blockquote><ul><li><a href="https://www.gitbook.com/book/97-things-every-x-should-know/97-things-every-programmer-should-know/details"><i>97 things Every Programmer Should Know</i></a> ~ Git Book</li><li><a href="https://www.amazon.com/Things-Every-Programmer-Should-Know/dp/0596809484"><i>97 Things Every Programmer Should Know</i></a> ~ Paperback</li><li><a href="http://www.extremeprogramming.org/rules/pair.html"><i>Pair Programming</i></a> ~ ExtremeProgramming</li><li><a href="https://www.agilealliance.org/glossary/pairing/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'pair*20programming))~searchTerm~'~sort~false~sortDirection~'asc~page~1)"><i>Pair Programming</i></a> ~ AgileAlliance</li><li><a href="https://martinfowler.com/bliki/PairProgrammingMisconceptions.html"><i>Pair Programming Misconception</i></a> ~ Martin Fowler</li><li><a href="https://readmedium.com/pair-programming-guide-a76ca43ff389"><i>Pair Programming Guides</i></a> ~ Medium</li><li><a href="http://wiki.c2.com/?PairProgramming"><i>Pair Programming</i></a> ~ wiki.c2</li><li><a href="http://wiki.c2.com/?PairProgrammingPingPongPattern"><i>Pair Programming Ping Pong Pattern</i></a> ~ wiki.c2</li></ul></article></body>

Step 64: Pair Program and Feel the Flow~

This is the 64th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 63rd Step, read it.

Pair programming is not a “go faster” strategy, it is a “waste less” strategy (which often results in going faster) . ~ Kent Beck

Image Source: Reddit

What is Pair Programming?

Also, know as Pairing. It is an agile software development technique in which two programmers work together at one workstation.

Why do Pair Programming?

  • It is a team building social skill which will get the work done while building cooperation within the team.
  • It increases software quality without impacting time to deliver.
  • Even though 2 people working might mean less work done, instead it will add as much functionality with higher quality.
  • Helps new team-mate to speed up through the on-boarding process.
  • Helps Junior developer to sharpen their skill, while Senior developer can learn by sharing the knowledge.

How to do Pair Programming?

Do pair programming by following Ping-Pong programming.

  • One, the driver, writes code.
  • While the other, the observer or navigator, reviews each line of code as it is typed in.
  • The two programmers switch roles frequently.
  • In addition, each member performs the action the other is not currently doing: While one types in UnitTests the other thinks about the class that will satisfy the test.

Common Misconceptions in Pair Programming

  • You have to do pair programming if you’re doing an agile process.
  • Extreme programming forces you to do Pair-Programming.
  • I don’t need to try pairing because I know I won’t like it.
  • Pair-programming halves the productivity of developers.
  • It’s only worth pairing on complex code, rote code yields no advantage.

TL;DR Paired programmers are only 15% slower than two independent individual programmers, but produce 15% fewer bugs.

Go to the series.

Go to 63rd Step

Go to the 65th Step.

References:

Programming
Pair Programming
Software Development
Java
Android
Recommended from ReadMedium