One of the biggest culprit to website data traffic, if not the biggest, is images. Due to the increase in the number of devices with high resolution display, content creators have started using high resolution images to improve the look and feel of their websites. This results in large amounts of data needing to be downloaded by everyone, including those not using hi-res displays.
What was once a simple landing page had turned into a huge member-based system that involves stuff like integration with external service providers. True story.
Traditionally, front-end code is compiled locally, the generated files are included in the project and then pushed out to source control. This is a redundant step and one we should get rid of, especially if we’re using build servers like
New OS means fresh install, which is exactly what I did. I installed the latest Windows OS, along with Visual Studio 2015 and SQL Server 2014. Then I tried opening one of my existing projects running on LocalDB, only to
As a front-end developer, I’ve had my fair share of working with CSS preprocessors. Two of the most prominent preprocessors I’ve had the pleasure of working with are Sass and Less. They’re both great, and I still use both of
Loggly is a great cloud-based logging tool. It enables developers to centralise their logging to one convenient location, which helps reduce the time it usually takes to log into the server where the project is located, find the relevant log
I’ve used LESS for a little over two years now, and I just thought I’d share the things I’ve learnt about LESS that has helped me be more efficient and productive when working on the front-end. If you don’t need
I was searching for a simple timepicker directive, much like the one used in Google Calendar, for one of my projects. I couldn’t find any, so I built my own. Angular Timepicker Demo This directive creates a simple dropdown style