Re:Slack – Degraded service affecting multiple features
by ibero on Friday June 28, 2019 @09:03AM
(#20303831)
The commenter above said they had to "solve live production problems", how exactly would "pre-defined tasks" help them?
[ Parent
| on HN ]
Re:Slack – Degraded service affecting multiple features
by pmlnr on Friday June 28, 2019 @09:07AM
(#20303861)
I slipped over the "live" word, but I still stand by what I said. I most probably work in a similar environment, with tonnes of live production issues, and I believe it's a result of not being allowed to proactively plan for situations - most of the issues are a result of cost savings, systems driven to their absolute maximum capacity, etc. Live production issues are a byproduct of moving too fast, breaking too many things.
Re:Slack – Degraded service affecting multiple features
by wastedhours on Friday June 28, 2019 @09:13AM
(#20303913)
I'd style my way out of that argument by saying out reliance on tools like Slack rather than other pre-planned work builds a reliance on that one tool for all tasks being done "in the moment", which then means it's relied on as the medium in live production issues.
If there was a lower reliance on IM for all tasks, other solutions for crisis management would be utilised (potentially).
Re:Slack – Degraded service affecting multiple features
by dasil003 on Friday June 28, 2019 @09:38AM
(#20304145)
What an incredibly arrogant generalization to make. You know there are also production issues created by moving too slow and failing to address pending scalability issues, right?
Re:Slack – Degraded service affecting multiple features
by pmlnr on Friday June 28, 2019 @09:59AM
(#20304323)
heh.
> failing to address pending scalability issues
How is that not related to not getting enough funding and resources?
And yes, having scalability issues means moving too fast - the _business_ moving too fast.