Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
BOFH
Monday 30th October, 2006 09:59 Comments: 0
Ah, the good old "ad-hoc" design. I saw this sentence in the latest BOFH and it made me chuckle:

"We could, but then we have service redundancy to consider and putting all our eggs in one blade basket, so to speak, could lead to a complete disaster. So it pays to have our services scattered on various servers in what appears - to the casual observer - to be a random and ad-hoc manner designed to increase our spend with a computing vendor so as to qualify for free conferences at holiday destinations."

Read the whole episode here.
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3