1. Performance Sketches
    Creating and enforcing performance budgets are hard to begin with, but getting everyone to understand the impact of their choices on the performance of a project can be doubly so. Having a way to "sketch" performance can help onboard new team members to the concept of performance budgets.
  2. Dude, Where's My Modal?
    Modals. Popups. Overlays. Dialog Boxes. No matter what you call them; ugh. I can't even. If I were being gracious, I'd say that nine times out of ten, modals are the lazy way out of solving a hard (or sometimes not so hard) design or development problem. We should stop doing that.
  3. CSS Strategy
    Updated on
    My current thoughts on this subject have been codified in [North](
  4. Empathy vs Understanding
    In order to solve the problems of our users or to work better with each other, we need both empathy *and* understanding.
  5. The Art of Keeping Up
    The web, as [Ethan Marcotte says](, is an inherently unstable medium. It's constantly evolving and changing, and in order to stay relevant you need to keep up. This is how I do it.
  6. There is no Enterprise
    Let's stop talking about "Enterprise". Enterprise code, enterprise design, enterprise color schemes, enterprise anything. As far as I can see, there is no such thing as "Enterprise", at least not any more, and not how it gets used.
  7. @target Your CSS
    `@target` syntax to spin out specific pieces of your CSS into new files through a little bit of post processing.
  8. What Can Blue Do For You
    After a fantastic 21 months, last Thursday was my last day at NBCUniversal and am joining IBM.
  9. Style Guide Questionnaire Results
    On April 21, I put up a questionnaire asking for feedback on how and why people use Style Guide systems. Here is the feedback I collected.
  10. Element Queries
    When building responsive sites, especially style and component guide driven responsive sites, being able to query an item's width instead of the viewport is invaluable for re-usability. While we don't have them natively, we can emulate them with JavaScript.
  11. Debugging Sass with Source Maps
    Updated on
    One of the super exciting features in Sass 3.3, currently in development, is the introduction of native Source Maps as a successor to Sass Debug Info. Working Source Map reading for Sass in Google Chrome Canary means this is a real debugging option you can start looking at today.