> then you divide the larger system into smaller components where each team is responsible for one or few of these individual pieces and the chief architect is responsible for making sure of how the pieces are put together
And then you have ravioli code in the large. It is not going to make it easier to understand the bigger system, but it will make it harder to debug.
Off topic but when I first saw ravioli code it was in a positive light, as a contrast to lasagna code. But then somewhere along the line people started using it in a negative manner.
There is some optimal level of splitting things up so that it's understandable and editable without overdoing it on the abstraction front. We need a term for that.
And then you have ravioli code in the large. It is not going to make it easier to understand the bigger system, but it will make it harder to debug.
https://en.wikipedia.org/wiki/Spaghetti_code#Ravioli_code
If you can reproduce an error, you can fix it. Do that.
If you cannot reproduce it after a day of trying and it doesn’t happen often, don’t fix it.