Friday 10 October 2014

Continuous Delivery at 7digital

I was asked recently by our head of product whether I could do an introductory run through of our continuous integration/continuous deployment practices (including why on earth we have them), as part of a series of 101 sessions our devs have been holding for the benefit of our product and UX team.

I jumped at the challenge: since I'm still new to the tech team, it's something that I've been trying to straighten out in my head anyway. It ended up turning into an actual presentation, and I just held a session on it with members from product, UX, and client operations.

The full slides are below, but I especially enjoyed drawing a number of mental lines from certain recurring patterns to specific steps in our pipeline:


I actually ended the presentation on a mini quiz, to see whether everybody could recall what the difference / overlap was between continuous deployment, continuous delivery and continuous integration, since I remembered that these always turned into a mush in my mind before I joined dev - admirably, my temporary students did very well! :)


3 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. First, the half is designed in detail together with precise dimensions and other structural specs. Prototypes are then made to provide a extra tangible pattern of the half. The objective here is to examine the construction and check it for stability, functionality, and aesthetics. If there are any errors or modifications to be made to the design, the prototype can be reconfigured and precision machining printed for a second evaluation.

    ReplyDelete