Presented by:Jake Witcher
Writing quality code involves more than just meeting requirements and passing unit tests. Good code clearly communicates intent to the reader. It is code that provides the shortest amount of time between the reader's first glance and an accurate understanding of that code. Reducing the time and effort it takes to understand the code you write will ultimately result in faster feature development, fewer mistakes, and easier bug fixes for your team. However not all software developers agree on what makes code readable. Programming language familiarity, comfort level with a programming paradigm, and personal preferences all contribute to a general feeling of subjectivity when it comes to describing code readability. Nevertheless, there are several characteristics shared by our differing perspectives and identifying these elements can help us understand not only what makes code readable for ourselves, but also what makes code readable to others. In this session you will explore how naming, arrangement, complexity, and statement type impact the time it takes the readers of your code to understand how your code works and why. By examining different implementations of each characteristic, you will better understand why developer opinions can vary and how you can work with your own team to create a definition of readable code that everyone can agree on.
Level: IntermediateTags:Back-End, Functional Programming, Other