Talking Architecture With Kevlin Henney

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 or 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. But if you want to create legacy code, make sure 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. The phrase 'small legacy system' can be considered 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.

About Kevlin:
Kevlin is an independent consultant and trainer based in the UK.
His development interests are in patterns, programming, practice
and process. He has been a columnist for various magazines and websites, including Better Software, The Register, Java Report and the C/C++ Users Journal. Kevlin is co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series.
He is also editor of 97 Things Every Programmer Should Know

For more engineering updates and insights:

* Follow us on Twitter → https://twitter.com/WixEng
* Subscribe our monthly newsletter → https://www.wix.engineering/subscribe
* Visit our blog → https://www.wix.engineering/blog
* Follow our Medium publication → https://medium.com/wix-engineering

Видео Talking Architecture With Kevlin Henney канала Wix Engineering Tech Talks