Lots of software gets built with less than perfect requirements. The results are typically less than ideal. Requirements need to be clear and precise but there’s more to delivering a high quality feature than just making sure all the requirements are met.
Learn how to optimize your workspace for pair programming.
Pair programming is exhausting. The level of focus required takes more energy than working by yourself. Learn to use it when it’s the most advantageous.
Experienced pair programmers claim that the code they produce is better than what they would have written on their own. But how exactly is ‘better’ measured?
Learn to pair program the fighter pilot way.
GitHub is becoming the one-stop shop for developers looking to work on open-source and private projects. In an effort to improve its foothold within the developer community, the company has recently improved its code review functionality and launched a marketplace for 3rd party developers to integrate with GitHub. This makes it a good time to look at how to make the GitHub experience more amenable to code review.
Developers and testers will often be on the same team, but accomplish drastically different tasks. A developer will typically write code, test the code, and document the feature. A tester will verify that the feature conforms to its requirements and find any bugs. Some of these tasks can happen at the same time whilst others can’t.