3 ms·
> I've encountered teams that use patterns like MVVM and VIPER, simply because they are designed to break projects into discrete components, so larger teams can
by ryandrake 5y ago
> I've encountered teams that use patterns like MVVM and VIPER, simply because they are designed to break projects into discrete components, so larger teams can work on them.
Yes, I've seen this kind of thing happen, too. Project complexity grows to justify the size of the team, not the other way around. A project that should take two good developers three months, gets assigned to a team of 40. That team has eng managers and eng manager managers and has to deal with all that communication and organizational bandwidth. We have all these people, so some of them must do core business logic, some of them will integrate 3rd party frameworks, some will do frontend/ui. And we need to take design time to draw the lines between these modules so nobody is stepping on anyone else's work. And we have to have stable APIs between all these, so we need an API design. Also, we need robust continuous integration and test frameworks because there are so many people committing, so we'll need to designate at least one, maybe multiple build engineers. And thanks to the tech lead / architect, we have many layers of abstraction, so the project can be mentally understood by 40 people. We also need to serialize and deserialize JSON between each layer, so that each could in theory be reused in a different project. Oh, and because of this complexity it's going to take the team ten months. A year and a half later, this massive CRUD app is released!
Meanwhile, two skilled engineers could have just sat together and developed that same CRUD app without all the complexity and layers of abstraction.