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

php - Migrating legacy procedural code to MVC without rewriting Front-end-Developer-Interview-Questions/French/README_FR.md at master · darcyclarke/Front-end-Developer-Interview-Questions panique/php-mvc Challenging CSS Best Practices Advertisement Editor’s Note: This article features techniques that are used in practice by Yahoo! and question coding techniques that we are used to today. When it comes to CSS, I believe that the sacred principle of “separation of concerns4” (SoC) has lead us to accept bloat, obsolescence, redundancy, poor caching and more. For those of you who have never heard of the SoC principle in the context of Web design, it relates to something commonly known as the “separation of the three layers”: structure,presentation,behavior. It is about dividing these concerns into separate resources: an HTML document, one or more cascading style sheets and one or more JavaScript files. But when it comes to the presentational layer, “best practice” goes way beyond the separation of resources. The Standard To help me illustrate issues related to today’s best practices, I’ll use a very common pattern: the media object7. Markup Result A New Requirement Comes In The image is now displayed on the opposite side:

Cache-busting the WordPress stylesheet Confirmation before closing of tab/browser Seravo/js-winning-style 10 Commandments of UX Strategy By Ronnie Battista Published: January 13, 2014 “I set out to frame what I have been observing in the UX strategy industry and hearing in conversations with others in the field. My hope was to capture the core, essential elements of UX strategy….” When considering my topic for the presentation that I gave at the UX STRAT conference in Atlanta, in October 2013—knowing that I would be speaking to an audience of respected peers and industry leaders in the emerging field of UX strategy—it was challenging to add something new or novel to the conversation. My interest in this topic came from a few places, including the following: The failed effort to create a UXPA International Certification program, which I undertook during my three years as Director of Certification for the UXPA. Here are some questions that I asked myself and the UX STRAT audience, which I’d like you to consider before we get to the Commandments. Ultimately, the two questions that I’m constantly asking myself are: Conclusion

Introducing MooTools Templated One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating: new Element Madness The first way to create UI-driven widgets with MooTools is creating numerous elements programmatically. template: The string HTML template for the class, including attach points, events, props, and subwidgets.templateUrl: The URL to the widget's template if it's external. When you desire for the template to be parsed and nodes to be created, calling this.parse() will accomplish that task. // The magical constructor initialize: function(options) { // Set the options this.setOptions(options); // Parse the template this.parse(); }, With the attach points and events in place, you can code your UI class per usual, using the attach points to refer to nodes when needed. Your UI widget has been created with flexibility and ease of use in mind!