Great info, could have used a bit less intro, but the talk itself had great coverage of the topic and was very helpful. Gemma is a very dynamic speaker and kept the audience involved. Wonderful.
Awesome talk! Very funny and well spoken! Thought you could slow down on your talking slightly, especially for those whom English is not a first language.
Awesome talk! Very funny and well spoken! Thought you could slow down on your talking slightly, especially for those whom English is not a first language.
Gemma is a lively speaker and understands her material very well. I can't think of a whole lot of feedback as I didn't see much that I didn't like. The content was well organized and at the correct level of detail for the talk length and audience. Well done!
Speaker had a lot of enthusiasm, but overall, I found the talk suffered the "bite off more than you can chew" syndrom.
Bad code, TDD, code duplication, S (without OLID), composer, PHPUnit, refactoring: a lot of different topics, all interesting, but in a too short amount of time. Especially after spending half of the slide/time on the intro.
I loved this talk (speaker is super engaging and the topic is very interesting to me), but I do wish there had been a bit less time defining terms and a bit more time breaking down spaghetti code into testable code :)
Loved the speaker's enthusiasm and broad background. Talk covered a range of topics, so lacked some depth. I might be interested if this was converted into a day 1 tutorial.
p.s. I think "Spaghetti" was a euphemism for fugly code. ;)
Well organized talk. Good use of examples in explaining the main techniques behind refactoring to make it easier to test your code. Also, nice to have the rationale behind doing this explained.
Gemma was a great speaker! Very enthusiastic and engaging, however I also agree with others that the time could have been spent better on the actual code examples and not on terminology.
Comments
Comments are closed.
Great info, could have used a bit less intro, but the talk itself had great coverage of the topic and was very helpful. Gemma is a very dynamic speaker and kept the audience involved. Wonderful.
Awesome talk! Very funny and well spoken! Thought you could slow down on your talking slightly, especially for those whom English is not a first language.
Awesome talk! Very funny and well spoken! Thought you could slow down on your talking slightly, especially for those whom English is not a first language.
Excellent talk. Learned some neat ways to make code more testable without necessarily chaning the code in its entirety. Excellent.
Gemma is a lively speaker and understands her material very well. I can't think of a whole lot of feedback as I didn't see much that I didn't like. The content was well organized and at the correct level of detail for the talk length and audience. Well done!
Speaker had a lot of enthusiasm, but overall, I found the talk suffered the "bite off more than you can chew" syndrom.
Bad code, TDD, code duplication, S (without OLID), composer, PHPUnit, refactoring: a lot of different topics, all interesting, but in a too short amount of time. Especially after spending half of the slide/time on the intro.
I loved this talk (speaker is super engaging and the topic is very interesting to me), but I do wish there had been a bit less time defining terms and a bit more time breaking down spaghetti code into testable code :)
Loved the speaker's enthusiasm and broad background. Talk covered a range of topics, so lacked some depth. I might be interested if this was converted into a day 1 tutorial.
p.s. I think "Spaghetti" was a euphemism for fugly code. ;)
Well organized talk. Good use of examples in explaining the main techniques behind refactoring to make it easier to test your code. Also, nice to have the rationale behind doing this explained.
I enjoyed this talk but agree with the other commenters that it could have used less introduction. Gemma was a great and engaging speaker however.
Gemma was a great speaker! Very enthusiastic and engaging, however I also agree with others that the time could have been spent better on the actual code examples and not on terminology.