4 ms·
Basically this promotes the idea of "full stack microservices". The problem is that many "full stack" people do not live up to their denomination and when you
by partycoder 9y ago
Basically this promotes the idea of "full stack microservices".
The problem is that many "full stack" people do not live up to their denomination and when you have all-full stack teams you are raising the odds for having people who are weak at backend engineering.
That is absolutely not something you want. Backend bugs can be catastrophic.
e.g: a guy in team checkout may not know what happens when you process currency with floating point numbers.
- icebraining 9y agoI think this is intended for large organizations, where you can have specialists on each team - e.g. instead of having a "backend team" of thirty developers and a "frontend team" of twenty, you might have five teams each with six backend and four frontend developers.