Why should any developer learn more than one programming language?
This is an interesting question. Let’s think of it this way: Does a carpenter only use one type of saw? Does a mechanic only have one type of wrench? No. In short the answer is, as craftsmen of code, we are only as good as the tools that we know how to use; and programming languages are those tools. When it comes down to deciding on what language it is that you want to learn, the question you need to ask yourself is this. What type of developer do I want to be?
In the everyday world, it’s usually a good thing to have what you need ahead of time, even if there’s a possibility of never using it: I’m going to school, better pack my books; I’m taking a flight this afternoon, better bring some earplugs; I’m going to a meeting, better bring a notebook, and coffee… and my phone. If I don’t end up using these things for the task at hand, no problem. » Read more: The Danger of Carrier Objects
As we start to build websites with mobile first in mind, our stylesheets can get messy really quick. In this article, we’ll talk about making your stylesheets more functional and easier to read at the same time. We will take a quick peek into SASS, and the benefits that it will have over your stylesheets. The focus will be about a common problem that I typically see regarding media queries. At the end of this article I hope that you have a better understanding about making your stylesheets easier to read using SASS.
ActiveMQ is a great messaging broker. However, using the default configuration is not recommended. This article will explain how I determined the appropriate ActiveMQ memory settings for one of our clients.
Gulp is quickly becoming the the leading task runner over grunt. If you are currently using Grunt or even worse, an ant task, then I highly recommend this topic for you. In this write up, we will quickly discuss Grunt, Gulp, and Gulp syntax.
After years of being immersed in Java development, I must admit that I got spoiled by its strong and mature ecosystem. Hence, whenever I want to pick up a new technology or programming language the following must be there:
Support by my favorite IDE (Eclipse or IntelliJ IDEA)
Mature building framework. It does not have to be Maven or Gradle but it needs to be at least better than Ant.
Easy TDD. This could be the trickiest one to achieve because not only do I need a testing framework, but it must also be supported by my IDE and build tool. Moreover, it must have an adequate mocking framework.
Groovy easily satisfies those criteria right out of the box. It has awesome support by IntelliJ IDEA, Gradle is written in Groovy and you can write JUnit 3-style unit tests.
Taking care of indoor plants can be work, especially if you have many of them. As you know water plays a major role in the health of plants, so lets automate it! Automation of watering plants can be cheap, fun and rewarding.
If you have ever practiced test driven development (TDD), then you are probably familiar with the TDD mantra – red, green, refactor. I’m a big proponent of TDD, but I think the TDD mantra is missing a fourth step.
Starting in Spring Security 3.2, developers gained an easy solution to their Cross-Site Request Forgery problems with Spring’s implementation of the Synchronizer Token Pattern. Spring’s documentation does a great job of explaining Synchronizer Token Pattern and their implementation, so rather than talk about all of that, I’m going to show you how to tweak their configuration so you can have greater control over the urls that are protected.