To really make configuration management work, you need to need to have sane process and architecture in place. Otherwise, you're just adding a layer of abstraction with a little automation sprinkled in, to an already shitty situation.
When configuration is done correctly, with an application that has solid architecture and configuration methodologies, configuration management can be incredibly beautiful. I've seen it done well, and it can be light yrs ahead of what basic bash or powershell scripting can do for you.
Suddenly, everyone is writing tests, testing locally, deploying canaries, getting demos ready 2 days ahead of time, and not deploying at 6PM on Friday.
A) That is exclusive/special to things like slack or pd. Seems like a lot of tools could handle this.
B) How those tools are related to being woken up. I exclusively use email for work notifications. Chat is purely for BS and chit-chat. The last thing I would do when woken up at 3 is check chat.
> Why the fuck are build/ops folks making decisions about how the application should be deployed and configured?
The answer is really easy -- the build/ops team is configuring, deploying and running the application.
Config tools aren't perfect, but they are better than the old school manual configuration or letting individual developers cook up special snowflakes to do things the "right". Way.
You should be using as close to one configuration management tool as possible, and as a developer, you should learn how that tool works.