How we write CSS has changed a lot in the recent years. Many developers do not write vanilla CSS at all anymore, BEM seems to be the industry standard for structuring the codebase but the advent of SPA’s has magnified it’s shortcomings. In some ways things have not
There is a bit of CSS that you will write or more likely use from a library that will influence your whole project. It is crucial and it’s quality and adequacy can make or break your productivity as you develop. That CSS is the famous (or infamous!) grid. Laying
With the rise of frameworks like React, Angular, Ember and the Web Components spec, the web seems to be moving towards a more components based approach to building apps. The abstractions for these are getting better, except for one part: CSS. In many ways, we write CSS just as we
CSS grid systems are incredibly helpful. They are one of the key components to make your HTML & CSS clearer and more concise, as they get rid of a lot of sizing micro-management. In the past, I've built upon InuitCSS which is a great and simple grid. For all projects
The technology around us is changing fast. What is not changing fast is people and processes that govern how we work together. All the best projects I’ve worked on had one thing in common: great communication, regardless of the odds. Thus one of my favourite trends recently is more
Although very popular, good and comprehensive AngularJS learning matarials are only starting to emerge. It's easy enough to jump into the framework, but no doubt you will quickly get stuck and with some misfortune, you could land on a well meant but outdated Stack Overflow answer. If I would start
1/06/2018 update: this blog post is now largely out-of-date and to make matters worse, I've lost the images during a migration. Although the principles still apply, tooling has changed, so your milage may vary. The Timeline tab in Chrome DevTools offers a peak into the stages of displaying
After reading an interesting article and watching this excellent talk from JsConf a couple of days ago, I've decided to look more closely at React. I've dismissed it when it came out, as it seemed to be flying in the face of everything we know about building the front-end (and
In one Google talk, Miško Hevery mentions that they wanted Angular to be used by designers. That statement can be dismissed easily. Angular is a complex beast and most people require a fair amount to get productive with it. I can easily imagine many a jQuery savvy web designer diving