Good high-level overview of debugging. I would have preferred more in depth coverage of some tools or techniques instead of the more generic content, but what you have is really well-suited for a diverse audience.
This was a good talk. It seems it was geared more for the beginner than intermediate or advanced developer, which is what I was expecting. Still, Colin was thorough and gave a lot of good information.
Really nice talk. It would have been better had you talked about some subjects in detail. For instance, when you talked about git bisect your example wash't completely correct. It would have been git bad {commit log #} or something like that. For someone that doesn't understand this concept it would have been unclear as to how to use it. Obviously google is your friend but still would have been nice for some detail here and there. Other than that great talk just thought to add some positive criticism.
This talk was very inspiring! Especially the parts about not giving up - something that's (unfortunately) so easy to do.
Margaret: I think the git bisect examples were correct - you do "git bisect bad" or "git bisect good". The commit # is optional. https://git-scm.com/docs/git-bisect
I felt that this talk was very well developed and executed. A bit focused on the junior audience, but that's okay. The challenge in talking about debuggers is that while they all involve similar tools, they're difficult to discuss specifically without using a specific toolset; I think the balance here was just right. Things for improvement might be a focus on intermittent bugs (e.g. figuring out what set of circumstances triggers an intermittent bug), and race conditions (which do happen). Overall, solid work!
This was a good talk backgrounded by sound advice and valid, helpful explanation and reminders of the right way to do things. I think there was a typo in this or his other talk in one of the quotes where it said siting when he meant sitting. I do feel he could have enhanced his talk by surveying the field of what others (books, presenters, blogs) recommend for a debugging approach, contrasting that with his suggestions, and maybe in the process taking out some of the details of how he came to his approach. It would be nice if the talk were more a holistic survey of the field of thinking about debugging than solely the author's thoughts, is what I guess I am saying.
Comments
Comments are closed.
Really helpful and gave a good breakdown of what the testing process should be for junior developers.
Very good talk, covered debugging completely in a very step-by-step way.
Good high-level overview of debugging. I would have preferred more in depth coverage of some tools or techniques instead of the more generic content, but what you have is really well-suited for a diverse audience.
This was a good talk. It seems it was geared more for the beginner than intermediate or advanced developer, which is what I was expecting. Still, Colin was thorough and gave a lot of good information.
Really nice talk. It would have been better had you talked about some subjects in detail. For instance, when you talked about git bisect your example wash't completely correct. It would have been git bad {commit log #} or something like that. For someone that doesn't understand this concept it would have been unclear as to how to use it. Obviously google is your friend but still would have been nice for some detail here and there. Other than that great talk just thought to add some positive criticism.
This talk was very inspiring! Especially the parts about not giving up - something that's (unfortunately) so easy to do.
Margaret: I think the git bisect examples were correct - you do "git bisect bad" or "git bisect good". The commit # is optional. https://git-scm.com/docs/git-bisect
I felt that this talk was very well developed and executed. A bit focused on the junior audience, but that's okay. The challenge in talking about debuggers is that while they all involve similar tools, they're difficult to discuss specifically without using a specific toolset; I think the balance here was just right. Things for improvement might be a focus on intermittent bugs (e.g. figuring out what set of circumstances triggers an intermittent bug), and race conditions (which do happen). Overall, solid work!
Would be great if your quickly showed setting up xdebug in PHPStorm really quickly in your slides.
This was a good talk backgrounded by sound advice and valid, helpful explanation and reminders of the right way to do things. I think there was a typo in this or his other talk in one of the quotes where it said siting when he meant sitting. I do feel he could have enhanced his talk by surveying the field of what others (books, presenters, blogs) recommend for a debugging approach, contrasting that with his suggestions, and maybe in the process taking out some of the details of how he came to his approach. It would be nice if the talk were more a holistic survey of the field of thinking about debugging than solely the author's thoughts, is what I guess I am saying.
Good and informative talk, some topics were too basic.
I thought this was a great talk because it focused on a process. In debugging, a process is far more important than any specific tool or technique.