anchor.diff:  
   
       
  -## Confession: We fulfilled all the practices on a checklist, but we failed on the core principle which is ‘to deliver changes quickly’
  +## _Confession: We fulfilled all the practices on a checklist, but we failed on the core principle which is ‘to deliver changes quickly’_
   
   Snap CI’s team had very enthusiastic and experienced CD practitioners. The team wanted to do ‘everything CD’. Within six months after we began the product, we had a microservices architecture with nine different components, sophisticated messaging queues, monitoring, an automated infrastructure, and deployment pipelines for all of these different components.  
   
  
positive.code: We learned that users don’t care if your team is practicing continuous delivery or using microservices. These are decisions a team makes to ensure what they build reaches users quickly and reliably. It’s easy to get caught up in the checklists, “doing CI and CD”, trying cool new microservices etc. 
  
  
  > _**Do the important things first that will deliver code quickly and reliably and then  evolve and move forward on your journey..**_
  
  
  The second lesson we learned was that CD is a journey. It's an evolution, and you first need to set your goals driven by your business and then make your way there. It is tempting to move to the latest practice or new technology as soon as you hear about it. However I recommend that  in the first few weeks, unless you are 100% sure that that's what you need, don’t make any major architectural decisions. Do the important things first that will deliver code quickly and reliably and then evolve and move forward on your journey.
  
negative.code: meta_keywords: "confessions, snapci, stories, experts continuous delivery, continuous delivery stories, monolith to microservices"
  summary_image: "/assets/images/blog/cd-confession-snapci/continuous-delivery-confessions-snapci.png"
  tags: CD Confessions
  ---
  <% content_for :banner do %>
  <figure>
  