The pMD Blog

Welcome to the
pMD Blog...

where we cover interesting and relevant news, insights, events, and more related to the health care industry and pMD. Most importantly, this blog is a fun, engaging way to learn about developments in an ever-changing field that is heavily influenced by technology.

Weekly Byte: Increasing Team Productivity with Pair Programming

In the world of agile software development, when two developers work on a software task together at the same workstation, we refer to it as pair programming. On the surface, it might seem inefficient to have two people taking on the same thing at the same time. However, at pMD we’ve found, along with many other people, that not only is pair programming no less efficient than working solo, it is actually more productive and results in higher quality code.

While counterintuitive at first, consider the following: when working on a programming task, the majority of the developer’s time is often spent understanding the code that needs to be modified, and then thinking about a good way to implement a solution to the problem at hand. This implementation ideally should be easy to understand and it also has to be carefully analyzed to ensure it won’t break any of the existing functionality in the system. Working with another person on these items is often much more effective than working individually. This is especially true if one of the developers is more familiar with the codebase than the other, but just having a second person to bounce ideas off of is extremely helpful.

So, how does one do pair programming? First, identify the task that you want to pair up on and select a colleague on the development team to work with. Then, sit down with your pair partner at a workstation - ideally one with two large monitors! Plug in a second keyboard and mouse, and you’re good to go! Starting from the design and analysis phase, all the way through implementation and testing, pair programming is truly collaborative. When it comes time to actually write the code, each person should take turns implementing pieces of it, explaining what they’re doing as they type. The second developer should follow along, ask questions, and make suggestions.

I’ve mentioned before on this blog that when you’re working at a busy medical software company there’s never a shortage of software development work waiting to be tackled. However, we’re trying to be more diligent about resisting the urge to each go off on our own when we do our programming work. Instead, we want to embrace the mantra that when it comes to software development, two minds are better than one. We know that increasing the amount of pair programming we do will help us write higher quality code and produce even more features that our charge capture and secure messaging customers need.
5G ACA Account Management ACI Advancing Care Information AHCA AHRQ AI Alternative Payment Model Android API Apple Artificial Intelligence Audit BCRA Best Place to Work Big Data bootcamp BPCI BPTW Bundled Payments Care Communities care coordination Care Navigation Care Team Career Fair CDC Charge Capture Charge Capture App Charge Capture Software Charge Capture Solution Charge Capture Statistics Charge Lag CHIP CIO Clinical Communication Clinical Data Registry Clinically integrated network CMS Communication Company Culture Conferences Connected Health Record culture custom reports Customer Interaction customer success customer support Customers cybersecurity Developer DHHS Dialysis discharge instructions EHR Electronic Charge Capture Encryption epidemic Expansion FDA FHIR Flu fundamentals GI GI Outlook Goals Health Care Health Care Technology Health Care Web Health Information Exchange Health Record Healthcare HIE HIPAA hipaa compliant communication hipaa compliant communication platform HIPAA-Compliant HL7 Home dialysis Hospital Census Hospital Communication IA ICD-10 ICD-11 Implementation Improvement Activities interoperability iOS iOS 8 iOS7 iPad iPhone iPhone 6 Lead Generation length of stay MACRA Medical Billing Medical Errors Medical Software Medicare Mentorship Messaging Messaging with Patients MGMA MIPS MIPS Registry mobile Mobile App Mobile Charge Capture Mobile EHR Mobile Health Mobile Messaging Mobile security Mobile Technology Modern Healthcare Native App Network news NIH OCM onboarding Oncology Care Model opioid crisis Patient Patient App Patient Care Patient Chat Patient Communication Patient Engagement Patient Generated Health Data Patient Handoff Software Patient Information Patient Safety Patient Visits Patient-Centric pmd pMD Team population health Population Health Management PQRS Product Development Productivity Promoting Interoperability QCDR Quality Scoring Recruiting Recruitment Reimbursement Remote Work reports Residents Responsibility ROI Sales Secure Data Secure Messaging Secure Messaging Video Secure Text Messaging Security Audit SF Biz Times SOC 2 success support TCM Teamwork technology telehealth Telemedicine Text Messaging texting training Travel Upgrades VA Value-based care Video Calling Video chat video communication video conferencing Wearable Device wearing many hats Web App Wireless Work From Home