Software architecture diagrams are a fairly common sight within the teams that I visit around the world. Some are hand-drawn collections of boxes and lines on a whiteboard, others are Microsoft Visio-style block diagrams on a wiki. The one thing that unites most of these diagrams is that they are abstract, out of date and typically don’t reflect the code. It’s 2016 though, why are most software development teams still hand-drawing software architecture diagrams using general purpose diagramming tools such as Visio? Not even the building industry does this! This article explores this topic and presents a simple approach for creating software architecture diagrams using code, so that the resulting diagrams actually reflect the code.

Een update vanuit het NLJUG bestuur met dit keer een feedback-experiment en de IoT Tech Day 2016.

In 1977 waagden wij de grote sprong: UNIX op de faculteitscomputer. Sinds de aanschaf van onze machine in 1974 draaiden wij het door de leverancier (Digital Equipment) bijgeleverde besturingssysteem RSX-11D.