The document discusses the importance of building complex software while avoiding complicated code, introducing the concept of cyclomatic complexity and its formula. It references multiple programming languages and tools for assessing code complexity, while emphasizing the need for clear explanations when code becomes complicated. The content touches on the role of software architecture and human readability in quality software development.

1. Complex is better
than complicated

2. We build complex
software

3. We don’t want
complicated code

4. Cyclomatic complexity
• M = E − N + 2P
• E = the number of edges of the graph.
• N = the number of nodes of the graph.
• P = the number of connected components.
• https://en.wikipedia.org/wiki/Cyclomatic_complexity

5. Limiting complicated code
• National Institute of Standards and Technology - 10
• Either
• Under the limit
• Provide a written explanation of why it become so
complicated

6. Software
• C/C++/Objective C - https://github.com/terryyin/
lizard
• golang - https://github.com/fzipp/gocyclo
• Python - https://github.com/rubik/radon
• Javascript - https://github.com/es-analysis/plato

7. It can’t help
• Stupid architect design
• Human readability
• Software Quality

8. Brought to you by Oursky
Build your mobile app fast
skygear.io (open source)