3 ms·
I can respect this, and acknowledge that there are use cases for all the infrastructure. My question is, are the trade-offs being considered? Not every use cas
by Enginerrrd 7y ago
I can respect this, and acknowledge that there are use cases for all the infrastructure. My question is, are the trade-offs being considered? Not every use case requires all the bells and whistles. It seems possible that development pipelines have moved towards using the bells and whistles in part because developers are familiar with them from FAANG use cases. People choose to use what is in use, often for good reason like there being greater documentation and support for a tool in heavy active use. But that doesn't necessarily mean you're using the right tool for the job. It involves weighing the reduced development costs with possible increases in deployment issues. There are a lot of companies with delusions of grandeur, trying to future proof for massive scaling issues that most likely will never come.
- james_s_tayler 7y agoYeah. I agree. Sometimes the trade-offs are balanced in favor of human factors more than the technical ones and it can skew the results in favor of solutions that aren't exactly a perfect fit, but they're deemed workable because you can find warm bodies willing to work on them .