Good explanation and very useful
Very useful, although we already use php unit extensively there is always more to learn.
Very good presentation. We had monolog already available but didn't use it yet. With the clear explanation from Florian Engelhardt I was able to use it immediately. Specifically his remark in keeping message and data separate.
Now we will add it - via traits - in our complete codebase - and build a small reporting tool to display to our support team.
Due the presentation of Florian tiny-awfull-troubleshooting - which I do mostly myself - can now be delegated to the teams and is actually fun to do.
Extremely touching talk: it certainly gave many folks food for thought for how we can **all** do better as community members.
For me this was just a big advertisement for Datadog, which is not a bad thing if the information given is good. But is was not.
The problem is that application logging within the code is hard to do. It needs lots of dependencies in all the places, and well for the scale the talk was about (bigger financial companies was the example) this was possible.
Log format or how a too format was just left in the middle.
And personally, the worst part was the fact they said application logging can be used for tracing and performance metrics.
These are different things and please don't encourage people to do so.
Demo could be better, but yes, live demos are never good. Just pre-record or screen capture it.
Information was a great and some good questions and answers.
Talk was mostly about hidden settings to tune the strictness of the analyser.
This in combination with several packages could give you the most optimal results... Or not, because turning it all up to "11" is also not a good idea.
Great overview of how DDD CAN be used, and not that you should use it all. The room was too small for the number of people there, so sitting on the stairs was the best option.
Great presentation with explanations and diagrams, but sometimes maybe a bit too generic or unclear.
Talk was mostly about hidden settings to tune the strictness of the analyser.
This in combination with several packages could give you the most optimal results... Or not, because turning it all up to "11" is also not a good idea.
The explanation was clear. We will not use it, but it was good information to make that decision.