I see thine image through my tears tonight,
And yet to-day I saw thee smiling. How
Refer the cause? Beloved, is it thou
Or I, who makes me sad The acolyte
Amid the chanted joy and thankful rite
May so fall flat, with pale insensate brow,
On the altar-stair. I hear thy voice and vow,
Perplexed, uncertain, since thou art out of sight,
As he, in his swooning ears, the choir’s amen.
Belovëd, dost thou love? or did I see all
The glory as I dreamed, and fainted when
Too vehement light dilated my ideal,
For my soul’s eyes? Will that light come again,
As now these tears come – falling hot and real?
One of the skills they pay me the
big bucks medium-sized Euro for at work is assessing the risks of changes going into production. To do it, I’ve become pretty good at evaluating the system that is being changed.
I could snow you with talk of checklists, metrics, and charts, but really, my most valuable analytical tools are my pattern-matching wetware and my experience. With those two things, I can usually describe the current state of the system and estimate its chances of going horribly wrong in the near future, just based on gut feel.
Below are my private terms for the various states of computer system health. I use different ones in official reporting. Usually.
- clean: The system runs smoothly, with no visible bugs. I read the logs to calm down after stressful meetings.
- stable: There are the occasional interface bugs, but the thing runs reliably. It feels like a melon you tap in the supermarket and decide to buy.
- scruffy: Most users hit some kind of bug or another, but they can make it work most of the time. Regular users have workarounds the way commuters have rat-runs that avoid traffic blackspots.
- buggy: This is when users begin to see the bugs they encounter as a pattern rather than individual occurrences. They start to wonder if the pattern of bugs indicates a deeper unreliabilty. They’re right to.
- brittle: Bugs aside, it pretty much works…right up to the point where it shatters into little tiny pieces.
- fragile: It falls over a lot. Ops can pretty much always get it back up again in a reasonable time. We spend a lot of time apologizing.
- fucked: It’s broken. Again. Fortunately, we have backups, and we’re fairly sure they’ll work.
- comprehensively fucked: The backups didn’t work. Shark time.
Entropy tells us that, barring intervention, systems tend to move down this sequence. But it’s not a linear progression. For instance, brittle and fragile, are parallel routes to fuckedness. They’re basically two different failure modes: the Big Bad Bang and Death by a Thousand Cuts.
The applicability of these categories to other matters is left as an exercise for the reader.
Cross-posted on Making Light, where any comments will live.
Catalog, Theodore Payne, Seedsman and Nurseryman, Los Angeles [cover], California business ephemera collection, courtesy, California Historical Society, CHS2013.1326 [a] and [b].jpg.
- buy it with thought
- cook it with care
- serve just enough
- save what will keep
- eat what would spoil
- home-grown is best
don’t waste it
Via Flickr Commons.
J.L.M. Lauweriks. Alphabet, . NAI Collection, LAUW 85. Via Flickr Commons.
Lauweriks was als theoreticus en praktisch kunstenaar van grote invloed op stromingen die aan het begin van de 20e eeuw opkomen, zoals de Amsterdamse School, De Stijl en Bauhaus. Hij was bovendien een belangrijke verspreider van de proportieleer of het systeemdenken.
As a theorist and an artist, Lauweriks exerted great influence on early 20th-century movements such as the Amsterdam School, De Stijl and the Bauhaus. He was also a key propagator of proportion theory and system thinking.