Comments by "Charles M." (@charlesm.2604) on "Twitch CEO Reveals His Thot Process" video.
-
1
-
@friarruse1827 Exactly. When we work on a large scale project we need to work within the boundaries of the version control conventions we use, everybody is constantly pushing and committing new code into new branches that is depending on other branches currently being worked on, if all those branches get merged into a final production branch the entire project is screwed and we have to rollback.
How do we avoid that ?
Continuous Integration pipelines, a set of automated routed changes to the codebase that verify the quality of code via robust testing, build all the necessary dependencies and binaries used throughout the whole architecture, update other parts of the infrastructure that are required for the new code to run properly and we have to document every step of the way, communicating with project managers, writing manuals and documentations for future uses, get the greenlight of all the other teams currently working on different branches, etc.
It takes days just to push a few lines of extra code written in 2 hours into the codebase and then weeks to push that updated version of the codebase from the development environment where we do our thorough testing into the production servers for end users to see.
I wouldn't be surprised if there were currently Twitch features that have been finished since Q1 and are still in stale progress, patiently awaiting the greenlight.
1