We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

A system is not a tree

Formal Metadata

Title
A system is not a tree
Title of Series
Number of Parts
133
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Trees. Both beautiful and useful. But we’re not talking about the green, oxygen-providing ones. As abstract structures we see trees all over the place — file systems, class hierarchies, call trees, ordered data structures, etc. They are neat and tidy, nested and hierarchical — a simple way of organising things; a simple way of breaking large things down into small things. The problem is, though, that there are many things — from modest fragments of code up to enterprise-wide IT systems — that do not fit comfortably into this way of looking at the world and organising it. Software architecture, design patterns, class decomposition, performance, unit tests... all of these cut across the strict hierarchy of trees. This talk will look at what this means for how we think and design systems, whether large or small.