The two, biggest problems in IT are cache invalidation and naming things. The third one, I think, is legacy code. If you’re not working in a startup, which has just been founded, chances are, you need to deal with some sort of legacy application. For a majority of my career as a developer, I was working in one company. It was great, but we’ve had to maintain an application, which was created around year 2002! That’s when Napster was shut down! Today, this application is still running, but since a few years, it only contains some of the functionality. The rest is being handled by a new app. In this post, I would like to share some experiences, how we dealt with it.
Continuing, what has become, an Angular2 series on my blog, today I would like to show you, how to internationalise your Angular2 application. You will learn how to tag your messages, how to build xlf files for translation and to configure your application.
Some time ago, Angular team introduced a CLI (Command Line Interface) tool for Angular2. It was created to help in development of ng2 applications. It can initialize a fresh app and serve it. It also has a support for webpack, so you can use it to build your applications. Today, I will like to have some play with it and show you how to make some use of this tool.
Have you ever wanted to create a custom dashboard from the data on your Google Analytics account? And for the dashboard to be publicly available? I recently wanted to add a “Top Posts” box on this blog. The problem is, it’s based on Jekyll, so is statically generated. I could have created some kind of plugin for jekyll (or maybe there is one), but I thought it would be cooler to get this data directly from GA. Obviously, you need to be logged in to access the Google Analytics API, which makes it impossible to use on a webpage. However, I have found Google Analytics superProxy. Today, I would like to show you how you can easily create an API with your GA data.