Sitting in a car dealership waiting for my car to be repaired gives a person time to think about the big picture. And so I found myself asking questions like:
- why is the shop open early and close early?
- why is the showroom open later and close later?
Just like a semi-tractor trailer that is not making money unless it's moving, a car dealership is also not making money unless people are working. An idle work bay is not making money. (just watch the staffing levels).
I'd like to say it's a conspiracy but it's not. It's practical planning. They are going for the sweet spot. The dealers want to show movement on both sides of the house without exposing new car buyers to repairs (warranty or otherwise). And they certainly do not want disgruntled customers near the new ones. They also want to the building to host both customers so that there's no wasted space.
I suppose it's not a terrible plan and it might actually be something that could be extended to manufacturing or software development. If ALL of the team were working on new code in the morning and then debugging and customer complaints in the afternoon then the CI/CD pipeline would represent actual work such that a deployment might have a fully vetted feature or fix in a single cycle instead over multiple cycles.
To be clear, I'm suggesting that when a fix or feature requires a team of contributions then the team should be working on the same feature at the same time so that they ting they are delivering is in sync with their peers.