3 ms·
> with over-fitted teams (do you really need 40 engineers to build this?) I've encountered teams that use patterns like MVVM and VIPER, simply because they are
by ChrisMarshallNY 5y ago
> with over-fitted teams (do you really need 40 engineers to build this?)
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.
I have also been told that we shouldn't use advanced development techniques, because other developers can't understand the tech.
The project that I'm working on, has a scope that usually is implemented by a team of 10 or more engineers. That's nuts. It's a fairly ambitious app, but it's just an iOS app. I've done a ton of these, alone. I also wrote the backend; which is not my forte, but I don't like the selection for backends, out there.
I have control issues, I guess...
> I’m essentially an advocate for hiring fewer people and with more precision.
So am I, but that does not seem to be how the industry works.
I remember talking with a startup manager, several years ago, and they told me that the entire industry is based around engineers never staying at a company more than two years; with 18 months being the norm. I know that they had a heavy turnover, during the two years we worked with them.
That has many, many downsides. Of course, you have the issue of "too many cooks spoil the soup," but you also have people writing code that they have no intention of maintaining, so why bother doing a good job?
I have always been of the opinion that we keep teams together for years. It helps them to become "unified," and "move as one." That pays off, big time.
But it also requires a completely different management style from what seems to be the norm, these days, and that, apparently, is too big an ask.
FWIW, I would have been happy with part-time gig work. No one wants to work with us "olds," though, so I have found people that want the work I do, and it is far more than full-time.
No money, but I don't really care.
- 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.