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
- Weird Amazon: An Exegesis of Loneliness - April 27, 2017
- Who Moved My Control Plane - April 27, 2017
- The Future Of SDN Is Up In The Air - April 24, 2017
- TELoIP and the SD-WAN Cook-off - April 21, 2017
- The Future of On-Prem in a Cloud World - April 21, 2017
- Rook is the New Flocker? - April 21, 2017
- Virtualization and Containers: All of This Has Happened Before - April 11, 2017
- TCP Terminators: An Expert Analysis - April 11, 2017
- Qumulo Secures Round C Prime Funding – My Conversation with Bill Richter - April 11, 2017
- CapEx on Cloud up 22% in 2016 - April 10, 2017