• Issue #16: DevOps

    Issue #16: DevOps

    Welcome to the sixteenth issue of De Programmatica Ipsum, dedicated to the subject of DevOps. In this edition, Graham explains why DevOps is the same thing as before, but this time is different; Adrian explores the current state of DevOps at the end of this decade; and in the Library section, Adrian reviews two major works by Bertrand Meyer: Object-Oriented Software Construction and Agile! The Good, the Hype and the Ugly.

  • Issue #16: DevOps

    Antonomasia

    Antonomasia is a word derived from the Greek ἀντονομάζειν, which means, "to name differently." It is a rhetoric figure of speech, or metonymy, in which a concept is named after another closely related. Classical examples are, for example "King" for Elvis Presley, or "Fab Four" for The Beatles. In technology, "Xerox" for photocopying, "Big Blue" for IBM, "Google" for searching, but (surprisingly enough) not "iPhone" for smartphone. In the software industry, a similar phenomenon happens: "C++" for object orientation; "Java" for web apps; "Jenkins" for CI/CD; "Python" for machine learning; "Scrum" for Agile; and Kubernetes for DevOps.

  • Issue #16: DevOps

    Play It Again, Sam

    While the phrase "Play it again, Sam" never occurs in the film Casablanca, the sentiment does. Sam is asked to play "As time goes by", a song about how some things remain the same despite the passage of time. The song was originally part of a 1931 Broadway musical, and perhaps ironically due to a musician's union strike when Casablanca was released, the studio were unable to release a new version of the song as a record. Instead, they re-issued the original version, recorded over a decade earlier.

  • Issue #16: DevOps,  Library

    Bertrand Meyer

    When the author of these words started its career as a software developer, "object orientation" was all the rage. "Serious" programming languages were object oriented. "Professional" programming environments allowed one to view "objects" and "classes" in all of their glory. Inheritance, not composition, was the way of the future. Design patterns names were the answer to actual interview questions.