Adding any kind of tracking to any project always seems to be an afterthought. Generally just before launching, a stakeholder puts their hand up and states that we need to track everything…. Usually resulting in lots of frustrating mutterings from all developers involved.
const plus compare
let and finally understand when to use the spread operator.
Working within a team or solo can adjust the development priorities but one that should always be high on the agenda is producing the best code possible.
Working on a clean, well organised codebase is bliss. It’s enjoyable and productive. Working on an unorganised codebase is annoying to say the least. It’s often frustrating, painfully slow to change and test anything and invites laziness.
Thankfully as CSS developers we have a handy tool called Stylelint that can help us avoid the unorganised situation.
PostCSS has been around since September 2013 and has been part of many developers workflow for a while. For those that haven’t had the time to dig into it and put some time aside to understand what it is and what it can do, this post is for you.
From the beginning of my web development career around 9 years ago I have always been fascinated by the fact that with a laptop anywhere in the world we can create and sell products online.
During my early development years the thought of creating products drove my passion to learn, read and experiment.
So after many months of procrastinating, designing and developing I’m happy to launch the beginning of Little Island.
Of course this is a big call, but having utilised various parts of this file on many occasions with large amounts of success, it sure does rank as an important resource, especially as server configuration is not my strong point.
So, what is this file I am talking about?