Let's build a parser


Comments are closed.

Interesting topic but the presentation could use a stronger and clearer goal. A few adjustments to the critical
Path and especially the demos would make it a great talk. A bit more practice and relaxation and the speaker can nail it much better. Good job! Keep practicing.

I found it a bit dry, many theoretical elements. Also I don't know if you actually convinced your audience to not use regular expressions for HTML parsing, but maybe that shouldn't be the goal of your talk.

Some suggestions:
* A more concrete example why using the techniques you describe would help. And might answer the question: why is it better?
* Most developers like numbers (performance even perhaps) perhaps throwing in a slide comparing numbers would illustrate the positive effect of the tools you described.
* I think showing implementations of existing tools, such as Doctrine or Twig would help
* The code was hard to understand, perhaps use pseudo-code or diagrams rather then actual code.

Also the screen you had to work with was way too small, something you can't help obviously, but didn't help clarifying code/demo.

I do find the topic quite interesting, but it's not a very sexy topic. If you, however, spice-it-up a bit. You can make this work. You certainly seem to know enough about it!

This is the kind of hardcore talk I really miss at many conferences these days. But because it's so hardcore I'd suggest to put less text and more images in the slides. Next to that it would be better to have code snippets in the slides (maybe with the classname as the slide title) instead of showing it right from the IDE.
Also I'd like to see the workings of the PDepend parser.

With those additions this talk will be more than awesome!

Hey Boy, first of all: job well done in bringing a high-level topic to the table, you did well.

A few remarks though, but just meant as improvements:
- make sure you put your code-snippets in your slides, that way you can keep eye-contact with the audience
- add a few sample use cases in how or why once should use a parser in a particular way
- be more fluent in your speech, as though you're discussing it with your colleagues or friends
- don't be nervous, you've talked before and you know you can do it!

Take note of these comments and apply them in the next few days and it will rock the house at DPC!!!

The subject was very interesting and very technical. Advanced stuff that I'm sure will do very well at the conference.

Some pointers:
- If you're not doing any live coding, just put the code on your slides. You'll have much better control over what is shown, how it is shown, and when it is shown
- Because the subject is so advanced and theoretical, your delivery is very important. You need to make sure things stay entertaining and captivating to prevent people from "zoning out"

That being said, you do picked a subject you really enjoy and care about, and it showed. Just practice and rehearse as much as you can, and I'm sure you'll turn this nice talk into a great talk :)

Thanks for an interesting talk; I am sure I will find a use-case for it ;) Code samples may be a good addition to the slides (instead of an IDE), and it would be also nice to start with an example, like

(term AND term) OR (term and term)

Starting with that, you can explain how you would create a parser to parse queries like these.

This is a Topic for a full day workshop. This is not easy to learn but hard to master ;)
Good Idea to keep the view relatively narrow.

Nice talk. Thanks

I agree with Michelangelo.