Refreshments and networking from 6:00 pm. Supported by NCR.
This event is free of charge and open to all. No registration required - just turn up.
Synopsis:
Systems get bigger, technologies reach further, practices mature, advice changes. Or at least some of it does. Some guidance remains unaffected by the passing of paradigms, the evolution of technology, the scaling of development. Break your software into small, cohesive parts defined by clear interfaces and sound implementations, all the while striving for simplicity. The excuses for not doing so are as predictable as they are problematic. If you want to create legacy code, make sure that the code is arbitrarily partitioned into large, incoherent parts characterised by unwieldy interfaces and incomprehensible implementations.
While there are many definitions of what a legacy system is, common to almost all perceptions of a legacy system is the concept of size — specifically, lots of it. There is a reason people don't complain about small legacy systems: it's practically an oxymoron. This talk sets out to re-assess and reassert the importance of thinking and implementing small as an essential property of software systems — yes, even the large ones.
