Source: medium.com
Why your code needs Continuous DeliveryCategory: Database, Kubernetes, Docker, Architecture
As a result, I had the “pleasure” to look into their current technology stack and codebase, which, despite being quite young, already had a high level of technical debt.
It is a much more fundamental level of technical debt and something we, as developers, have experienced repeatedly in our careers.
Given that every startup is different, and that there are hundreds of different technologies out there, I want to offer high-level advice that you can apply to almost every context.
Once you have picked the technology, all you have to do is: In just a few hours (2 or 3 if you’ve done it before, a day maximum if you are less experienced), you will have reduced your manual, repetitive work, set up some compelling quality constraints, and laid the foundation for a strong Engineering culture.
You might argue that it is too early a stage to know the architecture of your system and that it is going to change over time and, as a result, spending time on a CD pipeline would be a waste.
It is a much more fundamental level of technical debt and something we, as developers, have experienced repeatedly in our careers.
Given that every startup is different, and that there are hundreds of different technologies out there, I want to offer high-level advice that you can apply to almost every context.
Once you have picked the technology, all you have to do is: In just a few hours (2 or 3 if you’ve done it before, a day maximum if you are less experienced), you will have reduced your manual, repetitive work, set up some compelling quality constraints, and laid the foundation for a strong Engineering culture.
You might argue that it is too early a stage to know the architecture of your system and that it is going to change over time and, as a result, spending time on a CD pipeline would be a waste.
Related Articles
Community Partners
DevOps Careers