Sparked by a short Twitter exchange, this time I investigate why a lot of CD implementations (that I've come across) often appear to be half-complete or just fail to achieve CD. What are the root drivers behind achieving CD and why do so many implementations fall short? Is it just ME?It's a hard subject and one that I've debated with quite a few people. This episode is an exploration of a few themes and perhaps can offer some insights or perhaps is still a work in progress. I certainly have a few more avenues to explore around where the application stops and the CD implementation begins - plus should you design your CD implementation with that in mind.Really interested to hear your thoughts.SHOW NOTESMy book list including links to 'Accelerate', 'Continuous Delivery' and Domain Driven Designhttps://richardwbown.com/resources/The original tweet:https://twitter.com/BryanFinster/status/1587589240321626113Original post with my quote and Bryan’s discussion of it:https://riseandfallofdevops.com/5-minute-devops-cd-is-pointless-5c906d0fd164Bryan discusses many things including “Engineer for Release” on the No Nonsense Podcast:https://richardwbown.com/bryan-finster-continuous-delivery-no-nonsense-podcast/QUOTES02:19 - "in my experience over 25 years working in software on it, I've rarely seen an organization successfully deploy a consistent CD implementation across the whole org." [RB]02:52 - "continuous delivery is often seen as a holy grail for a firm's digital transformation" [RB]04:42 - "the organization types should be Westrum generative. That it should be a nurturing, encouraging high cooperation organization" [RB]05:16 - "So my point is most orgs don't support the concept of CD because they don't change. " [RB]06:02 - "Because as every good book on the subject says without fail, there is no one size fits all solution for any of this. Plus it takes a lot of work on the journey is really, never complete. " [RB]07:16 - "Most organizations are not software delivery centered organizations. There's just something that they have to do" [RB]09:36 - "Pride gets in the way when it comes to building software, but also CD pipelines." [RB]11:10 - "CD typically is created by a few heroes who understand that complex domain." [RB]12:34 - "Similarly for CD, perhaps that's too lofty a goal to aim for directly. If we look at this huge program of work that we take on when we start to implement CD." [RB]14:07 - " where does. the application stop and where to CD begin. But that's a, that's a topic for another time I believe." [RB]15:47 - "engineering for release, which I really love. This is the concept that you're building your release mechanism even before you've built the first line of code." [RB]16:01 - "Before you even write a test or a single line of code, you write your pipeline" [RB]

Ver todos los episodios