@kaiser what if in your case you need to catch the exception and log the error (notify your admin) but make sure the client side does not horribly fail? That is a good case to "go off and drink beer" in try/catch imo. Don't see a problem with your logic there...
hrm so you're saying not sure how you test IF you need to fix there or not? Sorry just asking to clarify as little confused?
yeah and logging should happen in background of course for sure... example in our case we have some processes that can throw exceptions if certain servers are down but still degrade gracefully for the user but send us log/push notifications to admin
If I understand you correctly ( I could be wrong ) why don't you just extend Exception and test for instance of SomeExceptionClass so you know what to do...
I was more about unit tests. I started using PHPSpec in this project - switching away from it as it's kind of not-major-enough and now I have to think about what happens if I unit test that. Kinda the wrong approach, but that's how it is now.
yeah this is also a strong point vs hipchat... HC is mobile too but its just not as strong as slack imo, even though HC should be better than slack in reality because its owned by Atlassian/BitBucket/Jira - they have far more money to dev the product than slack do... but they just are ass backwards sometimes
I have just set up and integrated loggly (credentials and connection). Don't log so far and the UI is quite overwhelming. If you know something better that has a free plan, please let me know. They got no phone app btw.