http://fredkschott.com/talk/ Recent content in Talks on Fred K. Schott Hugo -- gohugo.io en-us Tue, 22 Aug 2017 12:00:00 -0700 http://fredkschott.com/talk/2017-08-22-whats-next-for-polymer-keynote/ Tue, 22 Aug 2017 12:00:00 -0700 http://fredkschott.com/talk/2017-08-22-whats-next-for-polymer-keynote/ At Polymer Summit 2017, we announced a major change for the Polymer Ecosystem: our move towards ES Modules & the npm ecosystem. I was invited on stage to give the keynote address, introducing Polymer 3.0 and sharing the journey the entire Web Components ecosystem has taken since the early days of the spec. This is one of my favorite talks, not just because of its importance to the project but because it culminates a major, multi-year personal effort. http://fredkschott.com/talk/2016-10-18-whats-new-in-polymer-tooling/ Tue, 18 Oct 2016 12:00:00 -0700 http://fredkschott.com/talk/2016-10-18-whats-new-in-polymer-tooling/ At Polymer Summit 2016, our team introduced a major redesign of the Polymer tooling suite. This new set of tools was powered by shared utilities for common tasks like HTML analysis and element serving, and streamlined specifically to help users transition from beginner to advanced use. At the heart of this redesign was the Polymer CLI, which brings together these lower-level tools to create opinionated, best-practice workflows for building, testing, and serving Polymer projects. http://fredkschott.com/post/2015/02/performance-profiling-the-unexpected/ Thu, 12 Feb 2015 12:00:00 -0700 http://fredkschott.com/post/2015/02/performance-profiling-the-unexpected/ Performance testing a Node.js application can be painful. Tooling can be a nightmare to set-up, and online help is almost non-existent. And even with the perfect setup in place… what are you even supposed to be looking for? This is the position that we found ourselves in last year at Box, and this talk is the story of everything we’ve learned since. Instead of listing every relevant tool or teaching you how to setup awesome flame graphs, I share the surprising and unexpected things we learned about Node. http://fredkschott.com/post/2014/12/the-node-way/ Tue, 30 Dec 2014 12:00:00 -0700 http://fredkschott.com/post/2014/12/the-node-way/ Node.js has always been easy to grasp, but difficult to master. Design patterns and best practices exist for avoiding common pitfalls and building more stable applications, but these guiding principles have never been well documented. It has always been up to you, the individual developer, to uncover them on your own through painful trial and error. The Node Way is a new project to discover and document the entire Node. http://fredkschott.com/post/2014/10/how-to-interview-good/ Wed, 08 Oct 2014 12:00:00 -0700 http://fredkschott.com/post/2014/10/how-to-interview-good/ Boston will always have a special place in my heart. I went to school there, and in a lot of ways grew up there (in that way Millennials say they’re still “growing up” into their late 20’s). So when I heard that Box organizes a Boston recruiting trip every fall, I was desperate to get involved. The only problem? The trip requires interviewing experience, and I had none. So I started interviewing… a lot. http://fredkschott.com/post/2014/07/module-js/ Mon, 28 Jul 2014 12:00:00 -0700 http://fredkschott.com/post/2014/07/module-js/ Module.js is one of the most important modules in Node.js core, yet its existance remains almost completely undocumented. In this talk, I expand on my previous blog post by walking through the module and explaining how loading, compiling, and caching all work. If you’re interested in exploring Node.js core but don’t know where to start – or if you’re just curious about its inner workings – then this is the talk for you. http://fredkschott.com/post/2014/04/nodeup-cls-is-live/ Wed, 02 Apr 2014 12:00:00 -0700 http://fredkschott.com/post/2014/04/nodeup-cls-is-live/ NodeUp Episode #61 is now available at nodeup.com. I had a blast talking with Forrest Norvell, Trevor Norris, Dan Peddle, and host Daniel Shaw about CLS, AsyncListeners, and what it all means for Node.js v0.12 and beyond. Visit the site or grab the mp3 directly and hear a voice that was made for radio (but in the good way). http://fredkschott.com/post/2014/02/conquering-asynchronous-context-with-cls/ Wed, 12 Feb 2014 12:00:00 -0700 http://fredkschott.com/post/2014/02/conquering-asynchronous-context-with-cls/ In synchronous code, handling your context is easy. If you want to grab your current user or request data, you usually just pull it out of the ether. In Node.js it’s not that simple. There’s no thread to hold your context, and no ether to be found. So when you want to do something like logging, how do you attach meta-data without passing it explicitly down your call chain?