psychology dector

If you believe what you see, a fellow seems to have wandered into a shop at St Austell in southern England and accidentally destroyed several high-priced TV sets. It’s highly likely, though, that he was simply a professional actor who got paid for a smart publicity stunt. Click here to see this funny show.

The following video is a recording of the talk “ JavaScript coding tips ”, which I held 2014-05-16 at the Sud Web Conference in Toulouse, France. Bonus: See how I feel about comma first style (I was much meaner than I remember). I don’t personally like it, but I respect how creatively it solves a problem. Hear me speak French after the talk. Material: Slides “ Popular Coding Conventions on Github ” by Outsider : what coding conventions do people use on GitHub and how frequently? “ A Meta Code Style Guide ”, chapter 26 of “ Speaking JavaScript ”, which covers some of the topics of this talk in more depth.

The videos of the Google I/O 2014 talks have been online for a while now. Three of them are about Web Components and Polymer. This blog post briefly describes what they are about and mentions a few highlights, which may help you to decide which videos you want to watch. The three talks are: “ Polymer and the Web Components revolution ” by Matt McNulty (38:47) “ Polymer and Web Components change everything you know about Web development ” by Eric Bidelman (36:13) “ Unlock the next era of UI development with Polymer ” by Rob Dodson (41:30) If you need a quick primer to Web Components, you can look at slide 35ff of the slides for my talk “ Six technologies that will change the web platform ”. Polymer and the Web Components revolution Matt McNulty gives a broad overview of Web Components and Polymer, setting the stage for the remaining two talks. McNulty explains why Web Components are important, then describes Polymer , which is a Web Components polyfill plus a convenience layer on top. ...

JavaScript OOP is baffling: on one hand, there is a simple core, on the other hand, there are some really weird things going on. I’ve been pondering for a long time how to explain it well and I think the best way to do so is via four layers: single objects, prototype chains, constructors, constructor inheritance. The first two layers are JavaScript’s simple OOP core, layers 3 and 4 are where the complications start. The four layers of JavaScript OOP. I’ve explained the four OOP layers in an O’Reilly webcast: Video on YouTube (starts later to avoid duplicated content at the beginning) Slides Full webcast (requires Flash, but the audience’s comments in the chat are interesting) Additional material: “ In defense of JavaScript’s constructors ” explains my – conservative – recommendation of constructors “ JavaScript’s ‘this’: how it works, where it can trip you up ” Chapter “ Objects and Inheritance ” in the online version of “Speaking JavaScript”

On 2012-05-31, I held the talk “Fake operator overloading” at Fluent Conference , in San Francisco. The video is now publicly available (go there for a larger version of the video). The actual beginning of the talk (a few seconds where I say the talk’s title) is missing. But my mic test is there! ;-) Abstract: This presentation explains how to achieve a limited form of operator overloading in JavaScript. You’ll learn tricks that allow you to write code like this: var p = new Point(); p._ = new Point(1, 2) + new Point(3, 4) + new Point(5, 6); p._ = new Point(1, 2) * new Point(3, 4) * new Point(5, 6); Related resources: Slides The blog post that the talk is based on

On 2013-05-30, I held the talk “An overview of ECMAScript 6” at Fluent Conference, in San Francisco. The video is now publicly available (go there for a larger version of the video). And yes, I was slightly jet-lagged. You can download the slides on the official page of the talk.

Edge 2013 was a web development conference that took place on February 9, 2013, in London. Its approach was different from most conferences. Quoting the website : Edge is a different kind of conference, for developers with experience to share, who want to see and bring improvements to the web platform. Our emphasis is on creating a good environment for productive debate and discussion, rather than presenting the experiences of a single speaker. Each themed session is an hour long, and starts with a maximum 10 minute talk by an expert in that topic, outlining the current state of the platform in that area. [...] The remainder of the session will be given over to an open but structured discussion, with a professional moderator and a panel of seasoned developers who have in-depth knowledge of the subject. [...] Session participants will include [...] a notetaker to record the discussion so we can share it on the web later. Now the videos are online: Panel 1: Offli...