Session: Best practices of Pair programming and Code review
Teaching best practices of Pair-Programming and Code-Review afterwards
Although the global workplace allows people the opportunity to work with individuals from all over the world, there is still the challenge of knowing how to effectively communicate the ideas between software developers. For this Agile software development is practiced by many software companies like Google, Amazon, Facebook etc. To produce a significant development, it takes a huge round of planning a Sprint and predicting the tasks which can be achieved by the end of the Sprint. Therefore, it is crucial that all the team members are using their development time in a productive way not just reworking again and again. One good strategy for this situation is Pair-Programming. It enables two and more developers to think together on a common goal which leads to a great software product or solution in a short span of time. After the pair-programming the output piece of software codes needs to be reviewed by the rest of the team members. This step is very much crucial because more than two pairs of eyes can catch existing bugs, memory leakage in the code. In my proposed presentation, I will discuss how Pair-Programming and Code-Review can make every developer confident, courageous and possess a mind-set of giving constructive feedback to fellow team members.
Prerequisite: Basic knowledge of programming in Java, Agile methodology and GitHub or BitBucket
Bio: Sumana Saha
My name is Sumana Saha and I am a Software Developer by profession with around 6 years of experience. I am presently developing Microservices with Spring Boot, Apache Kafka, Docker, and Java 8.