SASS/SCSS is the compiled version of CSS, it allows CSS to be written in a more dynamic and reusable way. The philosophy is make CSS, a very static language, into something that is more similar to a scripting language, then the SCSS file is then compiled back into a normal CSS file to be deployed. y introducing variables and splitting the single CSS file into different SASS/SCSS files (will be combined into one when releasing), this makes the CSS much easier to read and more maintainable. This is especially true when more than one developer is working on the same code base.
I have been using Atom for more than a year, since it was in beta. There are many things I love about it, the most important thing is customizability. It allows anyone to create an Text Editor that is designed from the ground up for themselves. In this blog, I will be listing some of my favourite packages.
(Updated on 30th Jan 2017)
When using normal Windows mouse on a Mac, there were some weird acceleration applied to the cursor. After some quick research apparently there is this amazing free tool Smoothmouse which can simulate the mouse experience on Windows.
Came across this good library to display a large table on web pages. It is called handsontable, it is open source and seems very handy in some situations e.g. creating reports or needs to show large amount of data for some reason.
I have been a massive Vagrant fan since I was introduced to it in 2013/2014. To me, it is the first time I stepped into the world of DevOps and see the huge difference it made to a team. Before Vagrant, ensuring team member's machines and the server environments software versions is a huge headache. We always ran into issues where code works fine on one person's computer and ends up breaking on another machine. This is terrible news when the whole deployment process is meant to be automated. My Team had no choice but to increase the amount of manual testing done on the website to reduce these kind of issues getting through to production.
I am currently working on a personal project which involves the user entering their address to be searched. I wanted to ensure this application is designed properly, so it can easily be scaled to work with international postal address. However, after some research it is still far from clear what format I should follow.
I have been working with different fonts for ages, but never understood the difference. Recently, I have been working on a project where we need to decide a list of fonts to support. After some very basic research, here is what I found out.
For a developer sometimes it can be difficult to know what to focus on in terms of languages, frameworks and libraries. I came across this diagram created by devnetwork. It shows the top technology to focus on in different fields. Pretty useful way to measure yourself against, see what you already know and pick something new to learn in the future.
Today, I discovered a new tool which is very similar to Jira and Trello. I feel Jira is designed mostly for complex projects but can be a bit overkill for smaller/personal projects. Trello is very simple and straightforward to use, however, it lacks the ability to scale as the project unfolds. From a brief look at wll.space is very similar to Trello in this regard, simple but lacks scalability. Its design is what differentiates from the other two well-known applications.
If you have used Vagrant already then, you must know how powerful it can be when it comes to sharing local development environments. If you have not used it already, the whole idea is one person from the development team sets up a VM on their local machine then configure it with all the required libraries, settings and correct software versions. This VM can then be packaged up and shared with anyone.