background preloader

What is a Full Stack developer?

What is a Full Stack developer?
Is it reasonable to expect mere mortals to have mastery over every facet of the development stack? Probably not, but Facebook can ask for it. I was told at OSCON by a Facebook employee that they only hire ‘Full Stack’ developers. To me, a Full Stack Developer is someone with familiarity in each layer, if not mastery in many and a genuine interest in all software technology. Good developers who are familiar with the entire stack know how to make life easier for those around them. Server, Network, and Hosting Environment.This involves understanding what can break and why, taking no resource for granted.Appropriate use of the file system, cloud storage, network resources, and an understanding of data redundancy and availability is necessary.How does the application scale given the hardware constraints? Other Pieces of the Puzzle: Ability to write quality unit tests. Closing Thoughts: It is very bad practice to tightly couple code to a specific implementation (library, OS, hardware, etc).

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. So 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 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. Ultimately, the two questions that I’m constantly asking myself are: Conclusion

Seravo/js-winning-style Front-end-Developer-Interview-Questions/French/ at master · darcyclarke/Front-end-Developer-Interview-Questions 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. 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. Make Sure Your Baseline for Development Is Current A New Baseline for Front-End Developers, Rebecca Murphey Understand How Browsers Work Behind the Scenes

php - Migrating legacy procedural code to MVC without rewriting 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. You might be interested in reading Decoupling HTML From CSS1 by Jonathan Snook, On HTML Elements Identifiers2 by Tim Huegdon and Atomic Design With Sass3 by Robin Rendle as well. Please keep in mind: some of the mentioned techniques are not considered to be best practices. 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. The Standard Markup Result A New Requirement Comes In

Cache-busting the WordPress stylesheet