background preloader

Talks To Help You Become A Better Front-End Engineer In 2013

Talks To Help You Become A Better Front-End Engineer In 2013
Advertisement Many of us care deeply about developing our craft. But staying up to date can be a true challenge, because the quantity of fresh information we’re regularly exposed to can be a lot to take in. 2012 has been no exception, with a wealth of evolution and refinement going on in the front end. Great strides have been made in how we approach workflow, use abstractions, appreciate code quality and tackle the measurement and betterment of performance. If you’ve been busy and haven’t had time to catch up on the latest developments in these areas, don’t worry. With the holiday season upon us and a little more time on our hands, I thought it would be useful to share a carefully curated list of the most relevant front-end talks I’ve found helpful this year. Image credit: Jacob Bøtter Baseline Have a Strategy for Staying Up to Date How to Stay Up to Date on Web Stuff, Chris Coyier Part of continually developing your craft is staying up to date. Understand How Browsers Work Behind the Scenes

Introduction to Web Components W3C Working Draft 6 June 2013 This version Latest version Latest editor's draft Previous version Revision history Participate Discuss on public-webapps@w3.org (Web Applications Working Group) File bugs (w3.org's Bugzilla) Editors Dominic Cooney, Google, <dominicc@google.com> Dimitri Glazkov, Google, <dglazkov@chromium.org> Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Abstract This document is a non-normative reference, which provides an overview of Web Components. Status of this Document This section describes the status of this document at the time of its publication. This document was published by the Web Applications Working Group as a First Public Working Draft. Table of Contents 3 Templates

What I Learned From Brennan Dunn's Consultancy Masterclass Consultancy Masterclass Sketchnotes Consulting is something that I truly love. Helping businesses succeed, helping employees to stop focusing on mundane repeatable tasks, helping enterprises drive large scale commerce… these are truly activities that I enjoy. As a constant learner, I have a strong desire to learn from people that have already made my future mistakes, so that I can learn from them and avoid them. Brennan started offering his Consultancy Masterclass, and from the moment he launched, I’ve been extremely curious. The class itself is over the course of two half-days. Sustaining a consultancyPipeline managementMarketing and networking through eventsVetting and acquiring high quality clientsCultivating lasting relationshipsBilling and cash flowValue based rates vs. commodity ratesCulture (internal & external)StaffingBrandingOperations (remote v brick & mortar)Handling problem clientsProductized Consulting It was really crammed with information. “Awesome! Buy Sketchnotes Now

Polymer | Brillskills At their IO 2013 conference, Google officially launched Polymer, a new library for front-end development. It might seem odd that Google are launching another library, after all, they already have Angular, GWT, Dart Web UI and Closure, why create yet another one? However, Polymer is a bit of a different proposition that those libraries, and others like jQuery, Dojo, Knockout and Ember. Rather than creating a new API from scratch, Polymer is a collection of polyfills that attempt to implement upcoming standards, particularly those that come under the banner of Web Components. I’ve been following web components for quite a while, as it’s a technology I’m very excited about. I even created a Github project, Are We Componentized Yet? Google appears to have had similar concerns, and Polymer is their response. The idea is, while other libraries grow larger and larger, Polymer should actually shrink over time, as browsers implement features that are currently polyfilled.

Introduction to Web Components W3C Working Group Note 24 July 2014 This version Latest version Latest editor's draft Previous version Revision history Participate Discuss on public-webapps@w3.org (Web Applications Working Group) File bugs (w3.org's Bugzilla) Editors Dimitri Glazkov, Google, <dglazkov@chromium.org> Hayato Ito, Google, <hayato@google.com> Authors Dominic Cooney, Google, <dominicc@google.com> Copyright © 2014 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Abstract This document is a non-normative reference, which provides an overview of Web Components. Status of This Document This section describes the status of this document at the time of its publication. Work on this document has been discontinued and it should not be referenced.

Angular js for tech recruiters AngularJS and rethinking Web App Development | Cultivating Whimsy I stumbled onto AngularJS quite accidentally this year. I was beginning to think seriously about web app development in the context of an education technology idea, and was trying to pick between a plethora of third-party JavaScript frameworks that provide useful foundations and harnesses for quickly bootstrapping, building and testing an HTML/CSS/JS based web app. The main contention was between going with more established frameworks like Backbone.js and Ember.js, or taking a leap of faith with new candidates like MeteorJS and AngularJS. All of them advocated some type of design pattern for rapid prototyping, typically a flavor of Model-View-* which is particularly suitable for front-end clients that deal with RESTful backend services. With new JS frameworks appearing fairly frequently, it can be hard to stand out as a new entrant. MeteorJS AngularJS AngularJS on the other hand has taken a slightly different path to developer consciousness. Please join me.

AngularJS + Cloud Endpoints: A Recipe for Building Modern Web Applications Introduction Advances in client-side technologies are driving changes in the role of today’s web application server. Android, iOS and purely browser-based clients are powerful computing platforms in their own right. Their success has led to a reevaluation of ‘classic’ web applications. MVC frameworks, such as AngularJS, have been developed that enable client-side developers to build powerful and compelling UIs. AngularJS is a popular open source JavaScript client-side MVC framework supporting the rapid development of client-side applications. This paper provides best practices and guidance to web developers who are interested in AngularJS or other client-side MVC technologies and want to optimize their server backend for these technologies. Google Cloud Endpoints makes it easy to build a server-side API and encapsulate the backend boilerplate logic. The intended audience for this paper is Java developers with some experience with App Engine and a basic knowledge of JavaScript. Challenge

What is the difference between Polymer elements and AngularJS directives Story Estimation | tuesdayDeveloper; I’ve come up with the perfect explanation for how I would estimate stories. First, we are not measuring time or complexity—we’re measuring effort. For this example forget all you know—or think you know. Let’s ignore everything about T-shirt sizes or hours… instead we’ll think about vicious canines and the effort it requires you to render them unconscious in order to stop an attack. Escaping a chiwawa (not Phil’s, I’m sure they’re nice and not vicious and we don’t want to hurt them) doesn’t require much effort at all. Escaping a mastiff (you initially thought was a horse), however, requires a significantly larger about of effort. Who is providing the effort makes a difference. The actual effort required to halt the attack is the same in each case for each of us, the dog needs to be knocked out—same problem same amount of effort. The chiwawa is the story that requires the least amount of effort we have.

Related: