In this speaker's opinion, clarity is one of the most important properties of the source code. Code which is clear makes the tasks of extending, debugging, optimizing, or scaling straightforward, allowing the team to progress at a steady pace. Conversely, if the code is unclear, the team's ability to move forward is significantly reduced. Getting anything done takes much longer, bugs are introduced more frequently, the team energy drains, the morale drops, and people start to leave. To avoid such bad scenarios, code clarity should be given high priority, but sadly this rarely seems to be the case. More often than not we end up producing hard-to-maintain entangled mess which is very hard to work with.
This talk will take a look at some of the reasons why that happens and provide some advice which can help you improve the clarity of the code. The talk will go beyond mechanical reciting of design techniques such as SOLID principles, or metrics such as cyclomatic complexity, taking instead a more holistic view of the development process, exploring how various practices such as code reviews, evolutionary design, refactoring, and testing can be used to help you improve the clarity your codebase.
What will the audience learn from this talk?
The audience will gain a better perspective on why should they care about the clarity of their code and what can they do to improve it.
Does it feature code examples and/or live coding?
Slides might contain an occasional code snippet. There will be no live coding nor demos.
Prerequisite attendee experience level: