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.
Since I started using Sublime Text 2, I have fallen in love with the simplicity design. Compared to other more "robust" integrated development environment (IDE), it was faster to run, more customisable, had a large community and some of the functionalities are simply awesome. Since Sublime Text requires a payment of $70, it is a little pricey for me. After I had enough with pop ups telling me to pay the licence fee, I decided to look for an alternative.
There are many advantages of GPT disks compared to Master Boot Record (MBR). MBR was introduced back in 1983, any technology being that old has a restriction in modern day computing, and MBR is no other. If you are interested, feel free to read up on the comparison between MBR and GPT, but I won't be explaining the differences here. Instead, I want to explain the issues I had with GPT and how to resolve it.
Managing a large number of servers can be annoying, but a config file will make it much easier. Here I talk about how a config file can make all the difference.