3 ms·

I'm aware it is not unusual. It is not unusual for software to be badly written, too (being wide-spread is no sign of being a proper way of doing things). For

by dozzie 10y ago

I'm aware it is not unusual. It is not unusual for software to be badly written, too (being wide-spread is no sign of being a proper way of doing things). For a single project (and OP said it was one project) depending on that many specific tools coming from that many fields is a strong sign that the project does too much. Most of the tools mentioned by OP are from the set to be decided in deployment time instead of design time (log transport, storage, and browser, deployment automation, stuff like that), and they should not be dependencies.

markbnj 10y ago
The concept of a "single project" leaves a lot of wiggle room. In this case the "project" I refer to was a mobile application with all the front and back-end pieces that implies. You could carve the "project" up into sub-projects and view it however you wish, but since I was responsible for much of the back end pieces I experienced it the way I described.