Talk comments

Derek Binkley at 18:42 on 13 Jun 2018

The presentation and delivery was top notch. As a speaker I aspire to create the type of stage presence that Thijs exhibited. I also believe that the underlying message of reaching for the stars and taking advantage of the opportunities in front of you can inspire developers to take their careers to the next level. I definitely felt the talk was worth hearing, however, I had some issues with some of the undercurrents of this message.

The talk description ends in "even if it seems like the odds are stacked against you." I didn't get the sense that this was an overcoming odds type of story. I have heard other keynote speakers give similar talks whose stories involve overcoming homelessness, poverty, prejudice and more. In this story I felt that success was due to equal parts luck, privilege and hard work. I think that is fine but should be acknowledged that many others attempting to follow those footsteps must work so much harder and longer to get the pieces of their careers to fall into place.

Nic Wortel at 00:17 on 13 Jun 2018

A nice talk to introduce the concept of service buses. I think this talk could really differentiate itself from other talks about this subject by discussing the pros and cons of different styles of commands and command handlers - for instance commands with constructors and private properties vs commands with just public properties (allowing you to easily serialize commands from input, (Symfony) forms, etc), commands with domain objects in them vs commands with just primitives (encapsulating the domain object instantiation in the command handler), etc.

Nic Wortel at 00:06 on 13 Jun 2018

Not just a great introduction for people who want to start working with microservices, but also (and maybe especially) helpful for those that are already working with them and are experiencing some of the drawbacks listed in the presentation. I really liked how you not just listed the risks/drawbacks of a microservice architecture but also provided the audience with practical advice on how to solve/prevent them.

I do believe that you would be even more successful in delivering your message if you find a way to present the content in a bit more "lively" way. Especially for people new to the subject it might be a bit dry and hard to follow.

Nevertheless, a great talk!

Scato Eggen at 23:00 on 12 Jun 2018

Nice talk. Was there almost a reference to Battle Royal? ;)

Anyway, wanted to leave two tips, you probably know them, but just in case. Dryfus Learning Model (see Dan North) and Shu-Ha-Ri (see Alistair Cockburn).

Cheers.

Don't start a cat farm!!!!

Good workshop, but i do feel the first part of the workshop was better then the second half. Because there was so much to show still i really felt we went trough the react part a bit to fast.

I think this was partly because you wanted to also show the React native par(which was interesting by itself) and do the pair programming bit as well. Personally i would have liked to dive a bit deeper in the reactjs part itself where you could add as side-note that it should be easy to port this to reactnative and reactxp as well.

Nonetheless i enjoyed the workshop,

Nikola Poša at 16:10 on 12 Jun 2018

Big thanks to all of you who provided me very useful and constructive feedback! Slides are up: https://www.nikolaposa.in.rs/np/slides/dpc18/dealing-with-exceptional-conditions/

Super informative and interesting talk. Used solid argumentation to stress the importance of decoupling and clearly explains how one would go about achieving decoupled tests. Starting with the "Is this talk for you" slide was great, since it makes clear what to expect and what not from the talk.

Sander Krause at 13:54 on 12 Jun 2018

Fantastic talk, great atmosphere and no pressure to do things you're uncomfortable with. Some of us (including myself) broke out of our comfort zones during this session, which was really good to see. Valuable lessons to be learned, for sure!

Sander Krause at 13:51 on 12 Jun 2018

Not what I was looking for. A bit one-sided look at a code review (more like an audit -- I was expecting a review of changed code i.e. a pull request) with only two of the tools mentioned in the excerpt. The static code analyser contained some bugs, which made it slightly annoying to work with. I found reviewing solely through static code analysers to be quite limited, and discussion on what constitutes "good code" versus "bad code" limited by extension.

Miro Svrtan at 13:00 on 12 Jun 2018

Thank you all for such great reviews & feedback, means so much!

@DennisC: I tought I covered pair programming tools (I'we used hangouts & zoom.us, tryed Slacks tool but wasnt working for us then) and for video conferencing I would suggest to google around (I'we used both hangouts & zoom.us with OK results, unfortunately not perfect as conferencing 10 people can be tricky)