<story><title>I Watched All of the Chrome Dev Summit 2017 Videos</title><url>https://redfin.engineering/i-watched-all-of-the-chrome-dev-summit-2017-videos-so-you-dont-have-to-9b62a593c3cb</url></story><parent_chain><item><author>kinlan</author><text>Organizer of Chrome Dev Summit here.&lt;p&gt;Please do keep sending feedback and thoughts through on how can keep improving.&lt;p&gt;In terms of session length, I can see that being an issue. We had strict union regulations, and a lot of content to get through and I took the decision for more but shorter length talks that we can expand with textual content after the event.&lt;p&gt;We also tried to keep the theme for day 1 to everything we&amp;#x27;ve learnt in the last year, so what is the new minimum bar for web experiences, how to load them quickly and how we&amp;#x27;ve done it in the real world with commerce and media experiences and wordpress and pwa.&lt;p&gt;On day 2 I wanted us to showcase where we think the web could be heading in the next year, specifically with more of a focus on developer experience (devtools etc, polymer, lit etc)&lt;p&gt;Not saying we hit all those goals, but I do feel pretty happy with the event as a whole.</text></item></parent_chain><comment><author>xenadu02</author><text>&amp;gt; We had strict union regulations&lt;p&gt;Can you clarify what this means?&lt;p&gt;In my experience it means paying for more audio, video, and venue staff because the existing folks have been on duty all day but the conference organizers don’t want to pay or can’t afford to pay for a) more people or b) overtime&lt;p&gt;I’ve done a bit of mix engineering and conference organizers are very myopic: why can’t I be as excited about their stuff as they are? They don’t think about what happens when this is your day job and if you don’t bring the hammer down you’ll end up working unpaid overtime every day of every week because every conference thinks they are the hottest most exciting shit since sliced bread.&lt;p&gt;One can assume Google is &lt;i&gt;able&lt;/i&gt; to pay more but made the perfectly reasonable business decision not to. The mystery for me is why you’re blaming it on the union?&lt;p&gt;Perhaps the venue completely prohibits longer days but every rate sheet I’ve ever seen simply quotes higher prices if you exceed a “normal” conference day length.&lt;p&gt;(I’m genuinely curious here but also being slightly sensitive: there are certainly abusive unions - Philly conference centers come to mind where you have to pay master electricians to carry tables and chairs into the venue - but it is far more common for people to be cheap-asses &amp;amp; blame the unions)</text></comment>
<story><title>I Watched All of the Chrome Dev Summit 2017 Videos</title><url>https://redfin.engineering/i-watched-all-of-the-chrome-dev-summit-2017-videos-so-you-dont-have-to-9b62a593c3cb</url></story><parent_chain><item><author>kinlan</author><text>Organizer of Chrome Dev Summit here.&lt;p&gt;Please do keep sending feedback and thoughts through on how can keep improving.&lt;p&gt;In terms of session length, I can see that being an issue. We had strict union regulations, and a lot of content to get through and I took the decision for more but shorter length talks that we can expand with textual content after the event.&lt;p&gt;We also tried to keep the theme for day 1 to everything we&amp;#x27;ve learnt in the last year, so what is the new minimum bar for web experiences, how to load them quickly and how we&amp;#x27;ve done it in the real world with commerce and media experiences and wordpress and pwa.&lt;p&gt;On day 2 I wanted us to showcase where we think the web could be heading in the next year, specifically with more of a focus on developer experience (devtools etc, polymer, lit etc)&lt;p&gt;Not saying we hit all those goals, but I do feel pretty happy with the event as a whole.</text></item></parent_chain><comment><author>inglor</author><text>Hey, thanks for taking feedback!&lt;p&gt;As someone who was invited to attend - I really wished the talks were more low level and technical. I&amp;#x27;d really enjoy talks about how things are implemented in Chrome, how the underlying APIs (for PWAs for example) work and so on.</text></comment>