Revisionist history has a rocky perception in the public imagination. But all it (should) refer to is a reexamination of the historical record in light of new or neglected historical information. Sometimes this is castigated as biased or politicized history, because it often bucks the norms of a given historical narrative. But if we realize that all history by its nature is a produced work, done through the lens of whatever age it is written, revisionism is most often defined as simply being written after the “canonical” work.
In that light, James offers us an entry, in the spirit of Allan Nevins, Charles A. Beard, and Kirkpatrick Sale, a revisionist history of configuration management.
The Technical Blog of James comments:
I’ve got a brand new core feature in mgmt called send/recv which I plan to show you shortly, but first I’d like to start with some background.
This is my historical perspective and interpretation about the last twenty years in configuration management. It’s likely inaccurate and slightly revisionist, but it should be correct enough to tell the design story that I want to share.
Image Credit: By Source, Fair use, https://en.wikipedia.org/w/index.php?curid=18306793
- OpenFaaS: Serverless for Containers Made Easy - October 18, 2017
- Just Say No To KRACK - October 16, 2017
- One USB-C Hub to Rule Them All - October 16, 2017
- How to Accept Email Based Payments for Free as a Freelancer - October 13, 2017
- Satyamania: Windows Subsystem for Linux - October 13, 2017
- Technical Debt in the Age of AI - October 12, 2017
- The Origins of Premises - October 11, 2017
- Technical Debt Really Isn’t All That Bad – The On-Premise IT Roundtable - October 10, 2017
- E Tu Pluribus Networks UNUM? - October 9, 2017
- The Life and Death of Digital Re-Presentations - October 6, 2017