Member-only story
Even junior developers need to gain familiarity with continuous integration and delivery because these concepts sit at the heart of modern development. These processes sit at the heart because they bind the work of a team of developers together. Many new developers coming from university (or being self-taught) have not really had the experience of working on a large codebase as part of a team. As a result, even if they have used these platforms, they may not really understand the point.
Let’s look at how these concepts work with the growth of a team. This is a fictional company with fictional events, but it’s meant to illustrate how a (very naive) development team could grow and strain and learn to use CI and CD the proper way.
A single developer
Most small projects are a single developer working on their own code. Code organization is flexible or non-existent. There is little need, as the whole codebase sits inside the sole developer’s memory.
The developer is really plays all the roles that are normally part of a larger team: they decide what they want to build (business owner/stakeholder), they prioritize when and how long to spend building each feature (project manager), and once done they hopefully test their work (QA).
