Talk comments

John at 16:35 on 26 Oct 2017

I really wanted to like this talk, but it was too disjointed and unfocused for me to get much from it. I was expecting a list of good tools and discussion of what they each do and how they differ from each other: more practical take-away's. I was hoping to learn, for example, what "cyclomatic complexity" means and how to reduce it, or why I should use PHPStan in addition to PHPMD but not bother with Phan (or whatever).

John at 16:31 on 26 Oct 2017

Very interesting and engaging discussion.

John at 16:30 on 26 Oct 2017

Just fantastic, Perfect. Great job!

John at 16:30 on 26 Oct 2017

Great presentation, really clear and engaging. However, it should have been marked as "beginner" not "intermediate". It was a very basic introduction to unit testing (and TDD).

John at 16:28 on 26 Oct 2017

interesting idea, but I had trouble understanding what was motivating it. I did not understand why the need for a separation of commands and handlers and introduction of command bus.

John at 16:25 on 26 Oct 2017

Too much information and not organized well.

John at 16:24 on 26 Oct 2017

Maybe I was tired after lunch, but this talk was boring and didn't keep my interest.

John at 16:23 on 26 Oct 2017

Not convincing. Clear speaker, interesting topic, but I felt like he needed to present more alternatives or arguments against his approach, which struck me as pretty controversial. I am very sceptical that your average developers would not quickly end up with unmaintainable code if they took this approach. I would guess that relatively few developers have the problem of getting stuck because they spend too much time on upfront design. Most developers would benefit more from taking a highly structured approach that involves following some simple rules, so they don't have to spend too much time worrying about design but still write clean, dry, testable code from the get-go.

John at 15:58 on 26 Oct 2017

Very good speaker and very good talk. His keynote was even better.