One of my favourite features of SASS is the ability to use loops to dynamically create your CSS classes. A good example of this is when you want to make a set of classes to use for changing the text colours and background colours of elements you would normally have to write CSS like this.
Here's a little demo video that I put together to explain
pushing/pulling with multiple remotes and how tracking branches make
this easier. It's one of the chapters from my "Git Adventures" talk,
but it didn't make it in to the talk in Amsterdam...
We are collectively making the step into network based storage. We should also make the step to run this effectively with maximum performance and minimal interference on a single network. It really can be pretty simple…
Which is more readable? releaseVersion = version.substring(0, version.indexOf('-SNAPSHOT')) or
releaseVersion = version[0..-10] ? I'm going to go with the first one because it’s easier to understand if/when something goes wrong.
If networking really is on the cusp of changing over, user experience has to be an input into the design process. This is a radical change in how products are conceived, built, and ultimately brought to market.
To separate logic of accessing data from the routes, we create separate modules to handle the task of data access. When I started learning Node.js, a common pattern that I saw in some samples to separate the data access logic from routing was as follows: