Sebastian listed 26 things (if I counted correctly) to think about in order to write clean code, fortunately with examples in PHP at some places.
It might have been better to do a shorter list but with more examples?
In the beginning of the talk he said that he had prepared a 60 minute talk, not a 45 minute talk, and that probably spoiled it for both him and us. It was rushed sometimes, and did not finish on time. He also seemed to often read directly from his notes rather than speak freely on the topic.
All in all I would have expected better from such a high-profile speaker.
Expected a lot more from this speaker and subject.
Sebastian seemed to be a bit bored having to do this talk, which - in my humble opinion as a non speaker - could have been made more enjoyable very easy. It can be made a lot of fun to confront people with mistakes they're making on a regular basis. It came across as Sebastian was thinking "I'm just giving this talk because a lot of people asked me this question. Why do I even need to tell you guys these things that you all already should know anyway?"
Also just mentioning the topics in your sheet without any content and just nice pictures makes the talk even more boring. If you so clearly read from your laptop, at least allow us to read with you. Complex, but - I assume as I did not follow - beautiful and meaningful, phrases came from there, but I think they would have come across better when also put on screen.
Also, at the very least, a differentiation should have been made in widely accepted best practices and opinions, which I think for example was the remark about not needing comments inside methods. Though it did start me thinking.
So subject and contents probably ok, but the presentation was boring.
I lost track of all the different coding standards about 10 minutes in to the presentation. It was very generic, maybe pick the best 5 next time and tell a little more about them? Reading directly from the screen while we had to look at a nice picture is not great, but it gets even worse when you try to explain the picture. Maybe a good idea is a slide of key points per subject and maybe a bad (how not to do it) and a good example code sheet with every subject. This would require way less talking on your side, and a lot more attention on our side.
Very disappointing, sounded like the speaker was just reading Wikipedia articles on the topic. Way to little detail and depth to be usable in practice.
First, Sebastian kicked off by telling us he had prepared a talk for 60 minutes so he would have to rush things. The rest of the talk indeed had a very rushed feeling to it, and it was very clear he was just reading from his laptop screen. In terms of contents the talk felt more like a summary that you could've grabbed off wikipedia easily than a well-designed narrative.
There was no time left for questions or comments, which is a missed opportunity since this is such a grateful subject. By just focusing on a few topics and interacting with the audience the talk would have been much more engaging. I interrupted at some point to point out the principle behind rubber duckie debugging but Sebastian did not pick up on this.
All in all I think that an experienced speaker like Sebastian could have done much better with this material.
Sebastian made very good points that everyone should be reminded of now and again, but the way he presented it was a tad boring; most of the talk he was just reading from a sheet of paper. That made the talk a lot stuffier than it could have been. He really does know his stuff though, which is nice.
It takes a long time to master some of the practices explained in the talk, thus I tend to appreciate these kind of reminders, not to mention the remarkable work Sebastian is always doing in favor of quality.
I think to much information was pushed into this talk. Focusing on the most import ones with some more examples would remove the rushing part of the talk.
The sheets were beautiful, bit simply boring. More information on the sheets would also make it easier to follow.
All in all, the talk was a bit boring to follow, but a huge amount of very good information.
Content: nothing you couldn't find in "Clean Code" for the most part BUT this is no bad thing. All presentations work this way. It's an excellent book and the content was solid.
However, the speaker had such little interest or enthusiasm I honestly wondered what he was doing there. Would definitely avoid future talks if they were this laboured.
Comments
Comments are closed.
Good overview. Adding more examples will be better for a next time.
Nice overview of all rules, but nothing new that cannot be read in the 'clean code' book.
Didn't learn too much, some more examples should be better.
Sebastian listed 26 things (if I counted correctly) to think about in order to write clean code, fortunately with examples in PHP at some places.
It might have been better to do a shorter list but with more examples?
In the beginning of the talk he said that he had prepared a 60 minute talk, not a 45 minute talk, and that probably spoiled it for both him and us. It was rushed sometimes, and did not finish on time. He also seemed to often read directly from his notes rather than speak freely on the topic.
All in all I would have expected better from such a high-profile speaker.
In the beginning a bit low on examples but I guess that was partly due to the time constraints. Good overview of clean coding principles.
Expected a lot more from this speaker and subject.
Sebastian seemed to be a bit bored having to do this talk, which - in my humble opinion as a non speaker - could have been made more enjoyable very easy. It can be made a lot of fun to confront people with mistakes they're making on a regular basis. It came across as Sebastian was thinking "I'm just giving this talk because a lot of people asked me this question. Why do I even need to tell you guys these things that you all already should know anyway?"
Also just mentioning the topics in your sheet without any content and just nice pictures makes the talk even more boring. If you so clearly read from your laptop, at least allow us to read with you. Complex, but - I assume as I did not follow - beautiful and meaningful, phrases came from there, but I think they would have come across better when also put on screen.
Also, at the very least, a differentiation should have been made in widely accepted best practices and opinions, which I think for example was the remark about not needing comments inside methods. Though it did start me thinking.
So subject and contents probably ok, but the presentation was boring.
I lost track of all the different coding standards about 10 minutes in to the presentation. It was very generic, maybe pick the best 5 next time and tell a little more about them? Reading directly from the screen while we had to look at a nice picture is not great, but it gets even worse when you try to explain the picture. Maybe a good idea is a slide of key points per subject and maybe a bad (how not to do it) and a good example code sheet with every subject. This would require way less talking on your side, and a lot more attention on our side.
Very disappointing, sounded like the speaker was just reading Wikipedia articles on the topic. Way to little detail and depth to be usable in practice.
I came away disappointed from this talk.
First, Sebastian kicked off by telling us he had prepared a talk for 60 minutes so he would have to rush things. The rest of the talk indeed had a very rushed feeling to it, and it was very clear he was just reading from his laptop screen. In terms of contents the talk felt more like a summary that you could've grabbed off wikipedia easily than a well-designed narrative.
There was no time left for questions or comments, which is a missed opportunity since this is such a grateful subject. By just focusing on a few topics and interacting with the audience the talk would have been much more engaging. I interrupted at some point to point out the principle behind rubber duckie debugging but Sebastian did not pick up on this.
All in all I think that an experienced speaker like Sebastian could have done much better with this material.
It was like reading a book :-). Not a good presentation. Too generic. Would like to see more depth.
Sebastian made very good points that everyone should be reminded of now and again, but the way he presented it was a tad boring; most of the talk he was just reading from a sheet of paper. That made the talk a lot stuffier than it could have been. He really does know his stuff though, which is nice.
It takes a long time to master some of the practices explained in the talk, thus I tend to appreciate these kind of reminders, not to mention the remarkable work Sebastian is always doing in favor of quality.
I really hope Sebastian's new book, that we received a free copy of, will be more engaging than his talk, which was just plain boring.
I think to much information was pushed into this talk. Focusing on the most import ones with some more examples would remove the rushing part of the talk.
The sheets were beautiful, bit simply boring. More information on the sheets would also make it easier to follow.
All in all, the talk was a bit boring to follow, but a huge amount of very good information.
Content: nothing you couldn't find in "Clean Code" for the most part BUT this is no bad thing. All presentations work this way. It's an excellent book and the content was solid.
However, the speaker had such little interest or enthusiasm I honestly wondered what he was doing there. Would definitely avoid future talks if they were this laboured.