The Architect´s Napkin

Software Architecture on the Back of a Napkin
posts - 69 , comments - 229 , trackbacks - 0

My Links



Post Categories

March 2014 Entries

Evolution of a Basic Software Anatomy
In the beginning there was, well, chaos. Software had no particular anatomy, i.e. agreed upon fundamental structure. It consisted of several different “modules” which where dependent on each other in arbitrary ways: (Please note the line end symbol I´m using to denote dependencies. You´ll see in a minute why I´m deviating from the traditional arrow.) Then came along the multi-layer architecture. A very successful pattern to bring order into chaos. Its benefits were twofold: Multi-layer architecture ......

Posted On Saturday, March 22, 2014 10:42 PM | Comments (3) | Filed Under [ Software architecture ]

Lightweight Software Architecture on Napkins
Doing explicit software architecture is nothing for the faint of heart, it seems. Software architecture carries the nimbus of heavy weight, of something better left to specialists – or to eschew altogether. Both views are highly counterproductive, though. Leaving architecture to specialists builds walls where there should be none; it hampers feedback and flexibility. And not explicitly architecting (or just designing) software leads to less than desirable evolvability as well as collective software ......

Posted On Sunday, March 16, 2014 7:15 PM | Comments (0) | Filed Under [ Why a napkin? Software architecture ]

There´s no #antifragilesoftware
Antifragility has attracted some attention lately. I, too, pressed the “I like” button. :-) A cool concept, a term that was missing. Just when Agility starts to become lame, Antifragility takes over the torch to carry on the light of change… ;-) What I find sad, though, is that the discussion seems to be too technical too soon. There´s the twitter hash tag #antifragilesoftware for example. It´s suggesting, there are tools and technologies and methods, to make software antifragile. But that´s impossible, ......

Posted On Thursday, March 13, 2014 11:19 PM | Comments (3) | Filed Under [ Thinking outside of the box ]

What does Antifragility mean?
The notion of Antifragility has hit the software community, it seems. Russ Miles has posted a couple of small articles on it in his blog, asking what it could mean for software development – but also listing a couple of ingrediences he thinks are needed. I´ve read the canonical book on antifragility by Nassim Taleb, too. And I second Russ´ description: Antifragile software is software “that thrives on the unknown and change”. But still… what does it mean? “To thrive on the unknown and change” to ......

Posted On Wednesday, March 5, 2014 9:28 PM | Comments (1) | Filed Under [ Thinking outside of the box ]

Powered by: