Talk comments

Pim Elshoff at 14:19 on 10 Oct 2018

@PleaseMakeThisAnonymousNextTime
Thanks for being there, sorry I couldn’t connect to you

Goran Juric at 12:22 on 10 Oct 2018

This was a real keynote material talk and Miro nailed it. Having the discussion in the unconference track afterward was a really nice touch.

Only wish it was held on the first day so more people would hear it.

Davor Tomic at 07:36 on 10 Oct 2018

A well-prepared talk, with a number of real-life examples from which a lot could be learned. I liked how the speaker kept it interesting by switching from theory to practice for a number of talking points, so as to reinforce theory with practice and own experiences. I was amazed by some of the successful outcomes mentioned and wish Vladimir had time to tell a tad bit more about how to best decide which KPIs to measure, and how to best go about doing it. An idea for the next one, perhaps? :)

Davor Tomic at 07:29 on 10 Oct 2018

A bit dry at moments, but still worth hearing. Wouldn't say I learned a ton and it missed a deeper or personal note, sadly. The delivery could be a bit more engaging.

Davor Tomic at 07:27 on 10 Oct 2018

This is how you prepare and deliver a talk! Honest, spoken from own rich experience and filled with practical takeaways, Vladimir absolutely shined. Hope he gives more talks in the future!

Davor Tomic at 07:22 on 10 Oct 2018

The speaker raised many good points and gave good examples. Sadly, the mic issues made it harder to follow and the talk could use some more focus, which would result in one or few key takeaways.

Davor Tomic at 07:13 on 10 Oct 2018

Earlier this year I attended the Design Systems Conference in Helsinki, where I also participated in Nathan Curtis' workshop. My reasoning to sign up for Bermon's workshop was to go beyond what I learned in Helsinki and get my hands "dirty" by doing some actual coding. All with the aim of getting a better understanding of the "other side" of the process.

Unfortunately, seems like Bermon didn't expect so many of the participants to be designers.

Now, I can only speak for myself, and I thought the title and description both implied that designers were the target audience: "Streamline the design process and improve collaboration with developers by breaking down pages into reusable modules." – being the very first line of the description.
Another confusing bit was that the description stated "A basic understanding of HTML and CSS is needed", but it felt like what was expected was significantly more than that.

The decision was made to change the plan for the workshop and it seemed to me like it turned into a more theoretical lecture on pattern libraries, and any serious coding was out of the picture. Hence why I decided to leave after the first hour, with the hopes that at least the remaining participants will get their money's worth.

A few friendly suggestions for next time:
1) Test the title and description of the workshop and see what your test subjects would expect to find there (a simple survey or a round of interviews amongst designers and developers would do);
2) After people sign up, send them an introductory email with all the instructions and again a survey, so that you know your audience *before* you've already started to present [ a) designer/FE developer/both? b) knowledge of html/css/js/xyz? c) expectations from the workshop? ];
3) If there are instructions for installing certain frameworks or setting up development environments – all the stuff that >90% designers never did before – it would be much easier for them if these instructions were offered in the form of a video.

Better luck next time!

//Davor

AM at 20:35 on 9 Oct 2018

Although the trainer was charismatic and nice, this was in no way a good workshop, or workshop at all. The requirement for this workshop was to know basic html and css, which most of us did know, so it could have worked in our favor. Or write better requirements next time, so people won't apply for it. Most of the stuff on presentations were well know. But to be fair, first 2 hours were interesting and there were new things to learn, and that saves the workshop a bit. Still, it makes me sad we didn't go through with building the design library.

I have yet to see someone waste more post-it's then this workshop. Everything should point to actually learning how to make your code more DDD friendly and that part of the workshop was on 2 power point slides that were displayed for 2minutes. I had 0 idea how to do final exercise. So for next time, please skip 3h long post-it game since it's pointless and make all that content 10 minutes long. Then there will be more time to actually make something. Well actually I would be satisfied with just seeing some examples. Also I will copy/paste title of workshop just to make it more clear - "A practical introduction to Domain Driven Design (C#)". Notice C#? Last example was in PHP. ONLY PIECE of code shown was in PHP.