Great talk Mario, I used the library but I still had issues with understanding the concepts and you made it the right choice by going through the knowledge built within the library. But for english speakers or even non-native ones, you should might consider making your presentation shorter so you're able to speak slower since sometimes you might sound way too fast for them.
This is a great example how not to give a talk. No offense to the speaker, I'm sure he is very good in his field, and he seems nice. But he made some fundamentally wrong choices with this presentation. I would sum the issue up as, not starting out with code. He chooses to begin with an abstraction of his own solution. There are two issues here. First, abstractions are hard to grasp when you don't first understand the underlying logic. And second, he is giving us a solution without ever showing us a problem. Apart from "what is logging", he only briefly mentions it being better than print, because "you can do more", but never shows what problem he is actually solving. Unfortunately he gets stuck over-explaining his own abstraction, which is a common enough error. By the time he is half way through he has lost most of his audience.
I agree. There's definitely several real life examples we can take from the field to support how using the default Logging module properly could make your life easier. A little bonus slide could include things like Logging aggregation and the ELK stack.
Overuse of silly images during the presentation harms its quality.
The only think I understood was "We understand how logging works now right?" Nope.
Hello, viewer! Leave now and find a different video. This one only gets worse as you watch.
Great talk Mario, I used the library but I still had issues with understanding the concepts and you made it the right choice by going through the knowledge built within the library. But for english speakers or even non-native ones, you should might consider making your presentation shorter so you're able to speak slower since sometimes you might sound way too fast for them.
This is a great example how not to give a talk. No offense to the speaker, I'm sure he is very good in his field, and he seems nice. But he made some fundamentally wrong choices with this presentation.
I would sum the issue up as, not starting out with code.
He chooses to begin with an abstraction of his own solution. There are two issues here. First, abstractions are hard to grasp when you don't first understand the underlying logic. And second, he is giving us a solution without ever showing us a problem.
Apart from "what is logging", he only briefly mentions it being better than print, because "you can do more", but never shows what problem he is actually solving.
Unfortunately he gets stuck over-explaining his own abstraction, which is a common enough error. By the time he is half way through he has lost most of his audience.
Valid. I'm reading comments because I'm 7 minutes in and considering moving on to another video ...
Agree
I agree. There's definitely several real life examples we can take from the field to support how using the default Logging module properly could make your life easier. A little bonus slide could include things like Logging aggregation and the ELK stack.
Since I discovered structlog (www.structlog.org/en/stable/) I look back to stdlib logging with a shivering feeling only...
Corey has a video on logging that I recommend you to watch if this talk left you confused. ua-cam.com/video/-ARI4Cz-awo/v-deo.html
a little bit difficult to understand his accent(?)
Sorry about that :/ My accent is much better in Spanish :P
I watched the talk at 1.5x speed, and I still understood you just fine.
7even thanks a lot! If there is any part hard to understand or follow fell free to ask :)
subtitles are fine
lol please, the accent is easier to understand than the majority of british people's accents