This talk is about control, control our code, the flow, the tests and the complexity. It might be difficult to control the border of this country, but as a developer, we can take control of our code, can't we?
Reading code and maintaining code cost us time and money. “The ratio of time spent reading (code) versus writing is well over 10 to 1 ... (therefore) making it easy to read makes it easier to write. ("Clean Code: A Handbook of Agile Software Craftsmanship" - Robert Martin)
We can’t manage code complexity if we can't measure. It has been forty years since Cyclomatic Complexity was developed and published in the seminal paper “A Complexity Measure” by Thomas J McCabe.
What have we learned from this measure? Can this measure help us limit the complexity of our code? How to use this measure to guide our coding and testing? How to reduce our code complexity and make it easy to read and maintain?
This talk will look at a real-world problem and see how we can solve the problem with less complex code.