Last year I volunteered at Smashing Conf and I was honoured to be asked back. It's great to be able to give something back to the community and also help learn about 'back stage' issues that occur that many of the attendees will have no idea about.
Also, last year I was involved with running my first conference @upfrontconf. We had some great feedback from the community, and, so, we're doing it again this year (more details to come soon I promise! Thanks to those of you who have already shown an interest).
From my experience running @upfrontconf 2015 I have a tremendous amount of respect for people who do this. It's not easy. At any given moment something could happen, causing a lot of other things needing to be done, and fast. With the event all taking place on a specified date, time is a luxury you don't have.
Here are my notes from Smashing Conf 2016. I wrote these mainly for myself to jog my memory so apologies if things don't quite make sense. If you'd like something elaborating, please hit me up on Twitter and I'll try my best to clarify.
- Jam Session
- Day 1
- After Party
Wow, 36 trackers for The Telegraph, A/B split tests provided feedback to reduce this to 24 @smashingconf— Simon Owen (@s10wen) March 14, 2016
SVG optimisation is great to do, but be careful with automation as it can cause issues @smashingconf— Simon Owen (@s10wen) March 15, 2016
A site that is slow on http, is probably still going to slow on http2. We still need to think about perf basics @smashingconf— Simon Owen (@s10wen) March 15, 2016
To move to http2 requires https, this can cause issues when serving ads @smashingconf— Simon Owen (@s10wen) March 15, 2016
"Users aren't stupid, they're human" @smashingconf— Simon Owen (@s10wen) March 15, 2016
Wha!? Twitter stream in an email by pointing to CSS that's updated with content @smashingconf— Simon Owen (@s10wen) March 15, 2016
Day 2 Coming Soon…
Browse by category:
- case study4
- chrome dev tools4
- clojure overtone2
- dev tips1
- raspberry pi1
- responsive web design1
- web development2