The document discusses coping with complexity in software development. It addresses three main sources of complexity: 1) the size and interconnectedness of components, 2) the connections between components, and 3) the people writing the code. Managing complexity requires considering consequences, comprehension, and modifiability rather than just size. It also requires defining appropriate roles and responsibilities as well as focusing on the people aspects.

1. COPING WITH
COMPLEXITY
PETE GOODLIFFE ACCU 2011, Oxford, UK

2. @petegoodliffe
pete@goodliffe.net
goodliffe.blogspot.com
www.goodliffe.net
PETE
PROG
GOOD LIFFE
RAMMER / AUTHOR / C OLUMNIST / TEACHER CO NSCIENTIOUS CODER

3. 3

6. #1OF BLOBS
The complexity of our components

8. size isn’t the
enemy

12. consequences
comprehension
modifiability
harbouring future complexity

13. (the right)
roles and
responsibilities

14. my favourite

15. my favourite

16. my favourite

17. #2OF LINES
The connectedness of our
components

21. (bang)

28. #3OF PEOPLE
The people writing the code

29. “I know how to fix this
problem”
“make it a singleton”

30. QA &
Pete Goodliffe @petegoodliffe pete@goodliffe.net

31. blobs lines people
(components) (connections) (muppets)

32. @petegoodliffe
pete@goodliffe.net
goodliffe.blogspot.com
www.goodliffe.net

33. BUMPH DULL, but important
THIS DOCUMENT WAS CREATED BY PETE GOODLIFFE
IT IS COPYRIGHT // © 2011 PETE GOODLIFFE
>> ALL RIGHTS RESERVED
>> ALL THOUGHTS ARE OWNED
THANK YOU FOR READING // I HOPE IT WAS USEFUL
Version 1.0 2011-04-12