With so many different programming languages available, it is not always easy to choose the right one for a project. In this article, we will explore some basic criteria for picking the right one.
In the early-1990s, a lesser-known operating system was born named BeOS. It was an operating system that was ahead of its time, but was never able to gather much support.
I don’t like clutter. In fact, I am very picky about what I install on my computer which is one reason I love virtual machines to experiment with new technologies.
Since I am constantly starting a new project, I got tired of always having to set up each web app from scratch. Therefore, I decided to create a couple of boilerplate apps in Node.js and TypeScript.
Several years ago, I bought an old, colorful iMac G3 running Mac OS 9. It runs my old software wonderfully, but an emulated version of Mac OS 9 on my modern MacBook Pro is just so much more convenient.
I recently wrote a small script using TypeScript that can be used to determine the size of the view port using the breakpoints as defined by Bootstrap.
While adding a linter to an old project, I wrote the following bash script to convert 4-space indentations to 2-space indentations. This example recursively looks for *.js files starting at the script’s location. Of course, it can be used for any type of file though by simply changing the extension.
For about two years I have been using Grunt to compile my SASS files into CSS for projects for work as well as for personal projects such as this website. This workflow has served me well and I still use it for most of my PHP-based projects. However, I’ve come up with an even easier and faster solution for my Node.js-based applications.
Alex is a developer, a drummer and an amateur historian. He enjoys being on the stage in front of a large crowd, but also sitting in a room alone, programming something or reading a scary story.