Other answers do a great job of describing what you should do instead of isolating everything. I agree with them. What you are really asking for is extreme, however I will attempt an answer focused on the technical aspects of doing this when you find it warranted.
The assumption here is that you have found something that does need to be hidden and isolated ...
Since I don't have previous experience, I don't know how right/wrong my idea is and I would like your advice: am I on the right track?
If you don't have experience, and you are in the role of scrum master or project manager for a scrum team, the best thing you can do is step back and let the team make these decisions for itself. Your job as scrum master is ...
You are not Apple or Microsoft.
The reason why a software developer at Apple doesn't know about all of Apple's code is that there is a bloody awful huge amount of code and nobody can know about all of it. And there isn't one guy at Apple in charge of their repository. They have more than one :-)
What you are thinking about is just totally misguided. If ...
Why you shouldn't do it from a team perspective
The most important rules of project management regarding teams are:
The project can be a success only through intense teamwork.
Empowered teams that trust each other are the most effective.
One for all and all for one
What you are trying to do, is very different. It was called "Divide et impera" by ...
As far as I understood your question, the pure fact that people have different coding styles and design preferences is not a problem. A problem only arises when
the domains overlap and we need to collaborate
and these styles and preferences collide with each other. Now your plan is to solve that problem by "normalizing" the coding style.
To me, ...
It's tempting to think that customers reporting bugs to developers is useful and hence moving the TS team to be closer to dev can improve the product. But this is rarely the case.
Your dev and test teams are creating a product to a spec. they make compromises based on time and budget. Ideally there are zero defects.
Customers tell you whether the spec is ...