Hello my name is "if"

Me and my little brothers “else”, “elseif” and my bigger sister “switch” are most likely all over your codebase. Often we make your code harder to read or even difficult to understand. And don’t get me started on testing, we cause this thing called Cyclomatic Complexity, and I’ve been told that’s bad. Sebastian will show you that me and my siblings are similar but not equally bad even on a op-code level. He will show you some elegant and effective ways to get rid of us and make your code more comprehensible and easier to test. You want to understand the complexity metric, how it affects you and supports you to write more readable and maintainable code? Don’t miss this talk.

Comments

Comments are closed.

Erwin Deckers at 15:41 on 8 Jun 2019 (via Web2 LIVE)

A deep dive into making code more readable and more easily extended by removing traditional conditional statements.

Paul James at 21:15 on 8 Jun 2019 (via Web2 LIVE)

I loved the way Sebastian introduced the subject in a clear way and then went full on into a follow along real work example. Super practical advice and takeaways that developers can use today. Great stuff.

Chris Holland at 00:40 on 9 Jun 2019 (via Web2 LIVE)

Fascinating talk diving into the impact of if/else/switch on complexity, backed by explanation of opcodes equivalency, leading into a great run-thru of the Gilded Rose Kata with very insightful refactoring patterns and the “essence” of the open-closed principle.

Erik de Bos at 09:34 on 9 Jun 2019 (via Web2 LIVE)

I always admire speakers who can present a complex subject with clear, effective code. Well done!

Bas at 13:56 on 11 Jun 2019 (via Web2 LIVE)

I know many developers that should see your talk. I will use what you shared with me to explain them why I write code this way. Thanks for pointing out I should not skip to the next part of the refactoring until all of the code is ready for it. I tend to start on the next phase to soon because I think I can see what is coming.