[JohnFen]

It's not just a Slack issue, it's a general thing.

This puts the finger on one of the main reasons that I'm very concerned about the general state of software engineering these days. It's a lack of quality and stability.

Well, that's a little unfair. It's really that the industry is making a fundamental engineering tradeoff that I think is a terrible mistake: prioritizing rapid adaptation over robustness. We as an industry have decided that software should be ephemeral and disposable.

There are arguments for why that's a good tradeoff. We've been hearing them for years, and I was reasonably on board with the notion at the start (at least for some use cases). But I think that now that we've had experience with the results, my opinion has changed. I no longer think that the tradeoff is the best one.

[noir_lord]

I'm old enough to remember when we used to have prototypes and production.

Now it feels like we just have the prototypes in production.

[adminscoffee]

i think what happens is that things are 1. changing at a rapid pace and other things are just hype. i've switched or tested out newer languages and some were fun but, they didn't last because the trend died or they were bought out by facebook or some other tech firm and crashed. i've come to that keeping an eye out but not jumping ship until things look like the better option for certain. robustness plays a large part of my decision making these days. can it stack up to the weight etc