Talk comments

thiago marini at 12:55 on 6 Nov 2017

I'm afraid I thought the talk was quite a shallow, It gave the impression a PHP app can only exist in a monolith or follow only one architectural style. Nowadays we have a lot of options like serverless, microservices, hexagonal architecture etc... And it also gave me the impression you were a bit defensive. But you have the talent for speaking, keep going, you're good!

Jaap Migchels at 10:59 on 6 Nov 2017

Good talk, interesting approaches on how to deal with legacy material.

Could have done with a bit less code and more explanatory slides.

An excellent talk in terms of giving senior staff food for thought on how to manage their teams and make individuals feel valued and welcome.

Also an excellent talk in terms of giving the individual some good key points to evaluate if a role is worth their time.

That said, the talk did unfortunately nosedive at the end in the way it was delivered, which reminded me avidly of a preacher doling out a generous helping of guilt. This is not the way to spread a message of tolerance and equality.

Jaap Migchels at 10:56 on 6 Nov 2017

Great talk, very interesting material and certainly something to keep an eye on for the future.

Speaker was great and very approachable after the conference.

Some sections felt a bit rushed, probably too much material and too little time.

Jaap Migchels at 10:52 on 6 Nov 2017

Great first 30 minutes, really interesting material and some good book suggestions.

Could have done without the SWJ identity politics part though, aside from that, enjoyable and quite funny.

Definitely an interesting one and it was good to see a demonstration of all this.

While I did enjoy this talk I think it is definitely one that requires a fair amount of concentration and as such should not come right after lunch.

Superb talk.

Clear, well paced and spoken, easy to follow and very, very funny. Also, terrifying.

Funny, engaging and interesting. Everything a great talk should be.

Always good to hear about different approaches at working with old code.

I'd suggest taking more time when stepping through the examples to explain each step though.