Making an example up that I don't know to be true, but please just go with it: Google likely has a dedicated team who do nothing but tweak the front page of ww

Making an example up that I don't know to be true, but please just go with it: Google likely has a dedicated team who do nothing but tweak the front page of www.google.com I bet there's a Kanban-like board somewhere within that team with tickets like "change the button for image search to new branding icon" and "move the "About" button to the left-most upper corner from the right-most upper corner." "Make the corners on the search box more round" or whatever. Looking at the page now, somebody definitely had to generate work, and some poor front-end developer definitely had to perform the work to put the "Our third decade of climate action: join us". Every couple of years the team will take on some kind of task like moving the front-page to a new internal framework, or connecting it to some new search/advertising API. Remember when google would show real-time search results as you typed? "Let's put a Pacman game as the logo!" Here's Google's front page from 10 years ago https://web.archive.org/web/20130101000532/http://www.google.com/ https://web.archive.org/web/20130101000532/http://www.google... Somebody is making those changes, they exist. The decision to CD that page keeps them around. However, there is effectively almost no perceptible difference in the program performance, features, capabilities, or really even the aesthetics of that page in that time period to the user. It should be on maintenance mode with checking in on it being a part-time job for a single person. I bet that there's more than a dozen people who's sole job it is to keep that page "fresh". That's how CD results in inflated team sizes -- it's the "C". CI/CD never makes it over the wall into CM (continuous maintenance) and as a result becomes it.