{"id":9592,"date":"2019-04-24T10:30:15","date_gmt":"2019-04-24T05:00:15","guid":{"rendered":"http:\/\/innoroo.com\/blog\/?p=9592"},"modified":"2019-04-09T17:13:15","modified_gmt":"2019-04-09T11:43:15","slug":"non-solo-development-glossary-2","status":"publish","type":"post","link":"http:\/\/innoroo.com\/blog\/2019\/04\/24\/non-solo-development-glossary-2\/","title":{"rendered":"Non-Solo Development | Glossary"},"content":{"rendered":"\n<p><strong>Definition:<\/strong><br><\/p>\n\n\n\n<p>In Extreme Programming (XP), pair programming is a practice that suggests two developers should work together sharing one keyboard as they code. This is also a type of code review\/ design in real-time as one person watches when the other codes. The key benefit is better quality coding before the code is generated. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br><\/p>\n\n\n\n<p>Non-solo development produces higher quality code, code with fewer defects, and less technical debt. &nbsp;Most all of us have seen the chart that shows the cost of a defect growing exponentially during the development lifecycle. &nbsp;Fixing a bug in a maintenance mode requires someone (or a pair) to wrap their brain around often complex algorithms in order to understand the logic, make the repair, and not break something else. &nbsp;This is far more costly later, rather than when the code is \u201cfresh in your head\u201d.  Having a second set of eyes present while code is being authored often catches these bugs before they happen.       &nbsp;<br><\/p>\n\n\n\n<p><strong>Further Reading:<\/strong><\/p>\n\n\n\n<p>Book: Disciplined Agile Delivery by Scott W. Ambler and Mark Lines &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Definition: In Extreme Programming (XP), pair programming is a practice that suggests two developers should work together sharing one keyboard as they code. This is also a type of code review\/ design in real-time as one person watches when the other codes. The key benefit is better quality coding before the code is generated. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":9593,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[102],"tags":[105,2357],"class_list":["post-9592","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-glossary","tag-glossary","tag-non-solo-development"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2019\/04\/Non-Solo-Development.png?fit=3125%2C1709","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8Rui8-2uI","jetpack-related-posts":[],"_links":{"self":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/9592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/comments?post=9592"}],"version-history":[{"count":1,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/9592\/revisions"}],"predecessor-version":[{"id":9594,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/9592\/revisions\/9594"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media\/9593"}],"wp:attachment":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media?parent=9592"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/categories?post=9592"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/tags?post=9592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}