CSS Modules are mean of scoping CSS rules locally.
With CSS, one of the strengths is that styles are cascaded through the entire page structure. This can also be one of its weaknesses on a complicated page or SPA (Single Page App) – CSS you intend for one part can bleed into another. All fixable, but can be time consuming to track down.
CSS Modules (through the use of JavaScript) allow you to define CSS to a specific scope (set of DOM elements) – making bleed less likely.
It can also be used with PostCSS (linked to last week) as part of the CSS pipeline.
The project can be found here
This podcast talks about some of the experience of moving from Angular 1 to Angular 2.
One of the main takeaways from the discussion is that transition from 1 to 2 isn't easy. The benefits are there, but you need to think of Angular 2 as almost a completely different framework.
“… referring to high-achieving individuals marked by an inability to internalize their accomplishments and a persistent fear of being exposed as a "fraud"” Wikipedia
This really interesting talk discusses the Imposter Syndrome and how and why it affects developers (or any professional for that matter). If nothing else, it gives some great tips on public speaking.
Fun little graph in this article mapping the authors feelings about Angular during his learning curve.
Interestingly I’d expect that you’d be able use the same graph for almost every technical subject.
Great talk on how, as developers, we should be treating our code as human communication rather than machine instructions.
Again only one article this week;
Within my ROI series on LinkedIn, I've taken a look at the ROI of Failure. This article can be found here
The fourth article looking into Asp.Net Core is still in production. I've got Gulp working great for my CSS – just need to do the same for my JavaScript and write it all up.