- Monday: shyly open my inbox after a week of holidays, and probably duck to avoid the rolling ball of stale mail coming my way.
- Wednesday: maybe meet Karolina who’s in London for a conference!
- Thursday: my talk is closing a conference O_O — when the organiser mentioned “closing” the day I thought he meant closing the first day, not the second. NO PRESSURE. Although the conf is held at Shoreditch Village Hall, which is a venue where I feel like at home, so I’ll probably be OK. There’s a meatspace meatup afterwards, and I’m glad it’s around Shoreditch too or I’ll be dropping on that.
- Friday: MozFest facilitators meeting, and also the Science Fair during the evening (if it is still called Science Fair)
- Saturday and Sunday: MozFest, MozFest, MozFest! Paul Rouget asked me to show WebIDE there, and then Bobby (aka SecretRobotron and your best friend) came up with this idea of a MEGABOOTH where people can go and learn something about app-making in sessions of 5-20 minutes. Of course I can’t be all week-end there or I’ll basically die of social extenuation, so I asked some friends and together we’ll be helping spread the word about Firefox OS development in its various facets: Gaia/Gonk/the operating system itself, Gaia apps, DevTools and WebIDE. Come to the MEGABOOTH and hang with Nicola, Wilson, Francisco, Potch and me! (linking to myself and wondering if the Internet will break with so much recursion, teehee)
Here are the screencast and the write up on the talk I gave today at One-Shot London NodeConf. As usual I diverge a bit from the initial narrative and I forgot to mention a couple of topics I wanted to highlight, but I have had a horrible week and considering that, this has turned out pretty well!
It was great to meet so many interesting people at the conference and seeing old friends again! Also now I’m quite excited to hack with a few things. Damn (or yay!).
— CascadiaJS (@CascadiaJS) July 8, 2014
The news is finally out of the box! I’m speaking again at CascadiaJS!
I had a blast–no, make it A BLAST– past year when speaking there. I got super good feedback and lots of ideas after my talk, and the community was really welcoming and nice. I met tons of people who I have stayed in touch with since then, and whom I am totally looking forward to meet again! :-)
So I am super thrilled to be there again. There, but not quite there–because they make it happen on a different city from Cascadia each year. First year was Seattle, past year Vancouver and this year it’s Portland. (Maybe I’ll have the chance to play with those sweet arcade machines again…!)
I will be doing something different this time and not giving a purely technical talk. I’m going to talk about making the most of your failures (and turning them to your advantage!). Not sure how it’ll turn out, but if doesn’t go well, we’ll just embrace the failure ;)
Or: some of the few things I’ve learnt after a year of doing so and after giving feedback to people writing proposals too.
1) KEEP IT SHORT AND SIMPLE. This is the most important thing. Organisers often receive hundreds of submissions, and proposals will probably go through a first “screening” round. If your proposal doesn’t sound awesome at a first glance, it’s out. Done. End of the story.
2) Can this work as a talk? If it is a new subject, is it about Yet Another Framework that someone invented and has five users only? Would that make more sense as a blog post? If the subject is old and dull, can you add a different twist that makes it enticing and relevant? Maybe you can go a bit lyrical, but don’t overdo it!
3) Why should anyone watch your talk? What’s the expected outcome? Will it provide any specific value? Will people learn something? Will they be left speechless?
4) Don’t add links. If you need to link to something else you haven’t summarised enough. People reviewing proposals don’t have time to click on links.
5) Spellcheck and copywriting. Does this have a coherent structure? Does it even make sense? Does it have typos? Sloppy writing always leaves a bad impression on the reader, even if they won’t admit to it. Read it out aloud. Does it sound good? Can you read it with ease and not running out of breath? If you can’t, go back to rewriting. Shorten sentences, work on the rhythm, polish it until you make it beautiful.
6) Give it to someone else to read, and listen to their opinion. Preferably give it to people from different backgrounds-they don’t need to know the subject, but they can tell you if it sounds cool even if they have no clue about what you’re talking about.
I spoke at GOTO Amsterdam a few weeks ago. I was really thrilled to be back in the Netherlands after so many years! So thanks to Sergi Mansilla, who curated the HTML5 track, and the organisation in general for bringing me there!
The talk wasn’t recorded, but I made a screencast just in case you really want to listen to me. I am also posting the outline/notes I wrote, and they differ in places because I don’t read them during the talk (I don’t even have them handy) and I sometimes went a bit off topic, but that’s the beauty of improvisation!
On to the notes-expect some MASSIVE GIFs and amazingly clever photomanipulation! tee hee hee!